PRO+ Premium Content/SQL Server Insider

Thank you for joining!
Access your Pro+ Content below.
May 2010, Vol. 2

SQL Server index tuning for peak performance

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. ...

Access this PRO+ Content for Free!

By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.

You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

Features in this issue

News in this issue