Performance Monitor Counters

[This is preliminary documentation and subject to change.]

The implementation must provide performance monitor counters that allow an administrator or performance analyst to easily discover performance issues in a particular deployment. For the core OLE DB functions, these perfmon counters will be the same as the store perfmon counters. For OLE DB specific implementation such as the event interface, the OLE DB layer in the store will support perfmon counters that allow an administrator or performance analyst to easily discover how an out-of-proc sink affects the performance of the overall system. In addition, the OLE DB provider may instance permon counters by virtual server, similar to what is done by DAV, SMTP, and NNTP – but this is not required.

The list of perfmon counters supported are (all rate counters are "per second" counters):

• Cache Size Bytes (for Rowsets and other applicable objects)
• Row Bindings rate
• Row Bindings total
• Rows Modified rate
• Rows Modified total
• Rowsets Opened rate
• Rowsets Opened total
• Active TDataSources
• Active TSessions
• Transactions Started rate
• Transactions Started total
• Transactions Aborted rate
• Transactions Aborted total
• Transactions Committed rate
• Transactions Committed total