Finding table/index scans in execution plan and fixing them
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:
- CPU
- Network
- Disk I/O
Table/index scan creates all three types of bottleneck. Scanning every row of a table/index creates a lot of disk I/O due ...
Get Microsoft SQL Server 2012 Performance Tuning Cookbook now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
