What tools / methods do people use to monitor operation of EDBServer?

I have EDBServer running (on my server needless to say) sometimes super-busy, sometimes less so.

I have a few dozen users connected at most, often as few as 4 - 6.

Obviously I do what I can to optimize SQL and DB structure to minimize resource requirement on the server, I am just trying to delve a little deeper.

It would be great to be able to view the actual queries and requests hitting EDBServer, the time it takes to deal with each to give a result, whether a result is slow to return due to EDB itself, or due to some other OS issue, etc.

I am looking at EDB Configuration tables like "SessionStatistics" and "ServerSessionStatistics" which are useful, but hard to understand.

* Are there ways of seeing SQL hitting EDB Server?
* Are there third party tools for analyzing its function (like a DB-Workbench)?
* What do all you guys do about this?

Adam


This one

4.15 LoggedStatements Table (sql pdf manual)

was added by Tim fairly recently

<<* What do all you guys do about this?>>

I retired so I stopped worrying


Roy Lambert

Adam,

<< It would be great to be able to view the actual queries and requests hitting EDBServer, the time it takes to deal with each to give a result, whether a result is slow to return due to EDB itself, or due to some other OS issue, etc. >>

If you want to see *everything*, then you can turn on the tracing:

https://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=Starting_Configuring_Server

under "Configuration Reference", at the bottom you'll see a bunch of Trace* settings.

If you want to *only* see poorly-performing SQL statements, then you can enable the statement logging:

https://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=ENABLE_STATEMENT_LOGGING

Tim Young
Elevate Software
www.elevatesoft.com

Thanks for both of these responses. If I make a little monitoring utility I'll pop it in the NGs.

Tim

Does ENABLE STATEMENT LOGGING have any significant overhead for a typical EDB installation with 5 - 20 users?

My assumption is that since it is "only" posting a fairly small number of slower SQL statements to a system table it probably has v. little impact.

If that is the case I may well turn it on by default in my systems and add a screen to track "problem" SQL.