Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
I recently installed OAT and have begun to watch sql activity to find things
that may not be working right.
I came across a query that according to the system had a 10817 second response
time. The detail statistics don't show anything that would be out of the
ordinary and the query tree is just a simple index scan with a cost of 4 and
an elapsed time of 0.0000.
So the question is; what is "response time"? I looked at the help, but it
isn't mentioned.
Jonathon Wyza
CX & CBORD System Administrator
CX Programmer/Analyst
Administrative Computing
Bethel College
(574)-257-3381
AIM: Iamwyza
jonathon.wyza@bethelcollege.edu<mailto:jonathon.wyza@bethelcollege.edu>
==============================
SLES 11x64 & IDS 11.50.FC6
"Don't document the problem, fix it."
- Atli Björgvin Oddsson
Hi Jonathan,
OAT (SQL Tracing in particular) could be taking some data from previous run.
In my OAT in SQL Explorer -> Tracing Admin I see Oldest traced statement
pointing to my previous run of SQL Tracing:
1. I enabled SQL tracing on 2010-06-15 15:00 and run it for an hour
2. I enabled SQL tracing on 2010-07-01 15:00 and I see 'Oldest Traced
Statement' from 2010-06-15 - but I didn't save any data
Not sure that's the cause of your issue though.
The "Response Time" shown in the OAT UI is the execution time for that
statement.
If you want to know where OAT is getting that information... it comes from
the sql_runtime column of the sysmaster:syssqltrace table.
Erika
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.