Search results

ProTop also contains lots of code that will give you better insight into your database performance plus a ton of documentation explaining what those metrics mean. And you can easily entice us to talk about it by asking questions ;)

The values that you are seeing are just dumped directly from the VSTs (Virtual System Tables). Those are documented here: https://docs.progress.com/bundle/openedge-database-management-117/page/Virtual-system-table-summaries.html

BTW, 97.6% is not "very close to 100%". 97.6% is actually pretty crappy for a hit%. Using the example above if we assume a blazingly fast SAN with 2ms read repsonse time reading 100 records will take roughly 10.0001ms. Of that 10ms is waiting on disk, the 0.0001ms portion is operations in...

The hit% is the percentage of "db access" operations that do NOT result in a "db read". IOW, what percentage of logical activity is performed in memory? If you read 100 records, you have probably done about 210 "db access" operations (100 record block reads and a few more than 100 index entry...

There are many numbers in your post. Which ones do you think ought to be the same? Just guessing but a common misperception is that "db reads" are record reads. They are not. "db reads" is better read as "disk reads". A "db read" occurs when the database reads a block from disk. Which it will...

You should ensure that your database has been started with a non-zero value for -usernotifytime. This controls how frequently clients will check for schema updates. If the value is zero and a client is just sitting around doing nothing with the database (maybe the user went home for the weekend...

Progress 8.3 dates from the 90s. There were *ports* to many different platforms - HPUX, AIX, SunOS, Windows, etc but they are not binary compatible. As I recall the first Linux release was for 8.3e. And that required a SCO emulation package which has not been available with Linux for a very...

You have received a promotion!

You’re right. I got caught up in hyperbole. Obviously you should vote for things that you understand and support. I will edit my original comment to reflect that.

For those of you who may have forgotten... Progress has a portal for enhancement requests and there are a lot of good ideas there. Product management has also been a lot more responsive to these recently than they may have seemed to be in the past. If you have not been actively reviewing the...

Join fellow Progress/OE users in Burlington, MA Nov 12-15... PUG Challenge Americas is the premier event for those who design, develop and deploy applications based on OpenEdge and other Progress products. REGISTER NOW and take advantage of early-bird pricing! Over 50 sessions are now confirmed...

"Auditors want" is always a bit of a rabbit hole ;)

So "sudo". But with a license fee. And stuff.

I don't think it is the SQL engine per se that is doing that. I experimented a bit with the built in sqlexp tool and: 1) It does not return a count. 2) I can change the @ReportFormat from "standard" to "by label" with changes the output from what you describe to a format with no headers but...

It would not surprise me if there is a mismatch between your actual Java version and the Java version that OE9.1a expects. But I have no useful suggestions at this point. Other than the obvious - upgrade to a supported release.

You might want to consider sharing the name of tool that you are using to execute your query, the version of OpenEdge that you are querying, and the actual query being used.

I have added logging of such access, via OE Auditing, in the past as a result of “auditor concerns”. Part of that also involved writing some reports to demonstrate compliance. Or at least report on when the access was used. The work was done for a bank and I probably had to bill them for at...

This stuff was all 25 years ago... our memories are "dim". I believe that the properties file is just defaults. The -S that you provide on the sqlexp command line will override the one in the properties file. Speaking of command lines, your most recent example is not properly formed. You are...

Very old releases require the addition of a “-char” startup parameter to the sqlexp command line. https://community.progress.com/s/article/P92359

Sure. And as long as nobody finds out about the other port and tries to abuse it everything will be fine. I'm just saying: "don't trust the users to keep it straight".