Please see answers for your questions below : Hello, we are evaluating the trail version of DBTools 4 and trying to see if : it will help us speed us some SQL Statements. : Changing the statement around I am able to effect the values in the Trace : window, however, I'm not sure about what some of the values mean. : 1. : In particular the 'Gets', I can get this very low (89K to < 120), what : does this represent and am I correct in trying to get this as low as : possible. Gets is the total number of 'gets' including 'db block gets' and 'consistent gets', which equals number of all logical reads. In general, less reads is better : 2. : Do you have any other documentation on what you should hope to get the other : columns (Memory (K), Physical I/O etc.) to be for a full optermised : statement. : I know this is outside the scope of your product, but any links you have that : could help would be great. The answer depends on what your tuning goal is. there is no such thing exists as an fully optimized database forever and for all cases. Tuning requires a balancing approach. If your main goal is to reduce memory usage by various SQLs and applications so that more simultaneous sessions can run at the same time without causing memory swapping you would care about reducing memory usage first, but if you want your application to run as fast as possible by reducing the disk system and getting more data from the cache you may come up with a more memory, less disk solution. : Thanks in advance : Tony.
|