Access your Pro+ Content below.
SQL Server index tuning for peak performance
This article is part of the SQL Server Insider issue of May 2010, Vol. 2
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!
Features in this issue
Cool new features may not impress management, but return on investment always will. Speak an executive’s language when making the hard pitch for a SQL Server 2008 R2 upgrade.
Without the correct table indexes, SQL Server performance will quickly suffer. Here are a few tricks every DBA should know.
News in this issue
Business intelligence could prove to be an ideal specialty for SQL Server DBAs who feel like they've hit a wall with their current jobs.