Recent content by Rob Fitzpatrick

The amount of data you write to temp-tables, and where it is written and how it is read, can certainly affect your performance significantly at run time. In terms of tuning that, you should look at how large your DBI file is at its peak size and tune your temp-table buffers (-Bt) accordingly...

The question remains why the compilation of this program takes an "enormous" amount of time, relative to a larger program. Though you haven't confirmed the size of all of the source involved. Try to think of what is different about this particular program, compared with larger ones that...

One simple step you could take is to install SP08 and see if the issue persists. Even if it does, I'd say you're better off having those hundreds of bug fixes. I haven't used App Builder either, so I don't know what it does, or can be configured to do, during a save. It's also possible this...

Is 191 KB the source size with all of the include files (and their dependencies, if any)?

Is that actually what it says in the version file? In other words, you have no service pack installed? If you are dealing with a bug in a tool, it is important to know your service pack, if any. You haven't told us *where* you are doing this; it is relevant. Progress has several different...

Your version number, including service pack if any, is in %DLC%\version.

What does "saving" mean exactly?

It's called a NetApp. ;)

To me, measuring average memory consumption on a DB server doesn't make sense. That said, I really think your key to success will be to be able to get these numbers in real time, and OS metrics as well, while this internally-developed software is collecting its stats, so you are comparing...

It appears to me that Linux allocates all of shared memory up front, but different tools (top vs. htop vs. nmon) calculate things like resident set size differently and it's not clear to me which is correct. I suspect the OE broker's memory-allocation behaviour is going to be OS-specific and I'm...

The driver is for the use of the client, not the server. The client accesses the DB via TCP so the DB's OS doesn't matter to the client. Just specify the name or IP address of the Linux host rather than the Windows host when you set up your client connection (e.g. via a DSN) and you will be...

I'm not sure yet exactly what you're trying to do, or where SQL Server fits in. Where is the OpenEdge database that you want to connect to via SQL? (i.e. what is the OS) What is the client application you want to use to connect to this database? What OS does the client run on?

Are you referring to the OpenEdge SQL drivers? These allow you to connect to an OpenEdge database (assuming appropriate configuration) from a SQL client. There is a version of the OpenEdge SQL drivers (called "SQL Client Access" on the Progress download site) for each platform: Win32, Win64...

Off topic: That reminds me... last week I watched a PSC webinar about upcoming features in OE and some people were running terminal sessions in X-Windows. Twenty years ago I ran X-Windows in AIX on IBM RS-6000s and seeing the demo gave me a huge rush of nostalgia. :) I can't believe the UI is...

On the DB side: Buffer pool buffer, BI buffer, AI buffer... probably not a comprehensive list.