I often find myself wanting to know how many transactions per second
a database is committing to disk, as well as how many queries per
second it's processing. While Larry's busy making stats changes, I'd
like to propose a few more counters:
Number of commits: Ideally, this would only count transactions that
actually modify data
Number of statements: Simply, how many statements have been executed
Number of DML statements: how many insert/update/delete statements
executed.
For the last two, it would be ideal if they counted statements that
were executed inside of a function.
Having these counters would make it easier to determine what kind of
workload a server is actually handling. It's currently possible to
determine transactions over a time period, but the process is rather
convoluted and doesn't differentiate between transactions that modify
data and those that don't.
--
Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED]
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
