July 2012
Intermediate to advanced
478 pages
10h 3m
English
In most cases, especially while working with small amount of data from big tables, table scan/index scan should not be the desired way to go for. It becomes mandatory to find and resolve it in order to improve the performance, because scanning process goes through each and every row available in table/index, looks for match with the criteria provided, and returns the result set. This is really a time and resource consuming, heavy process. While working on performance tuning, people are afraid of several major bottleneck issues, mentioned as follows:
Table/index scan creates all three types of bottleneck. Scanning every row of a table/index creates a lot of disk I/O due ...
Read now
Unlock full access