This question is prompted by the new server properties introduced in Version 17...
The addition of those properties implies that the database properties of the same name may in fact be reliable; is that true? The question is important because historically the CurrIO database property has been so wildly inaccurate as to be completely useless.
So... can we now trust the database properties CurrRead and CurrWrite in SQL Anywhere 17? How about Version 16, and earlier releases? |
There was a change to address the inaccuracies of these I/O counters. This fix made it into the 17 release but not to branches before that. Hooray! Now I can un-comment the code in Foxhound, at least for V17 target databases, to display CurrIO etcetera... incomplete I/O can be a bad sign for performance.
(25 Nov '15, 15:26)
Breck Carter
|