Premium Content

Access "SQL Server index tuning for peak performance"

Published: 13 Oct 2012
Selling a SQL Server 2008 R2 upgrade

This article is part of the May 2010, Vol. 2 issue of Selling a SQL Server 2008 R2 upgrade

You can’t just create your indexes randomly. They need to contain the right number of the right types of columns. It’s a slippery slope. The wider the index is, the larger it is. The larger the index is, the slower it is. Slower indexes take longer to load from the disk, which means it will take SQL Server longer to process data in the index. Make sure that the only columns you index are those used to filter data, such as columns found in the WHERE clause of your query. Any columns that are being returned as part of the SELECT statement, or used to JOIN to child tables, should be added to the index as INCLUDE columns. For example, the following index query contains the correct columns. SELECT LastName, FirstName FROM dbo.Employee WHERE DepartmentId = 4 CREATE INDEX IX_Employee_DepartmentId ON dbo.Employee (DepartmentId) INCLUDE (LastName, FirstName) Below is a more complex query that includes the JOIN column in order to get a better view into columns that should be incorporated as either indexed columns or included columns. SELECT e.LastName, e.FirstName, ... Access >>>

Access TechTarget
Premium Content for Free.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Already a member? Login to access this content.

What's Inside

Features

More Premium Content Accessible For Free

Back to top