RE: Database tracking

[Terrian, Tom (Contractor) (DAASC)]

Title: Message

I guess I would also like to test out the network response time.  If I run the same SQL from one UNIX box to the production databases at other sites (via sqlnet), I can record total run time and sql statement run time (I assume the difference would be network response time?).  If I keep this information forever then I will know if the databases are slowing down or speeding up.  I could also determine if particular boxes are speeding up or slowing down.

 

The question is, what would be a good SQL statement to test?  Is

SQL> select count(*) from dba_tables;

as good as another?

-----Original Message-----
From: Jamadagni, Rajendra [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 15, 2003 1:09 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Database tracking

Statspack ??

 

Raj

______________________________________________________

Rajendra Jamadagni              MIS, ESPN Inc.

Rajendra dot Jamadagni at ESPN dot com

Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.

QOTD: Any clod can have facts, but having an opinion is an art!

-----Original Message-----
From: Terrian, Tom (Contractor) (DAASC) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 15, 2003 12:54 PM
To: Multiple recipients of list ORACLE-L
Subject: Database tracking

All, I would like to track the performance of my production databases by running the same SQL statement against each database every 5 minutes or so and recording the results.  For example:

sql> set timing on;

sql> select count(*) from dba_tables;

 

That was I would know if they are getting faster or slower over time.  As anyone already done this?  Would there be a good SQL statement to use?

 

Thanks,

Tom Terrian