Whether a query uses Scan or Seek can have a big impact on the cost of excuting that query. This article examines when each is used and which is optimal.  Read more...

Read more...

When created and maintained correctly, indexes help SQL Server retrieve data quickly. See how to ensure your SQL Server environment is running up to speed.  Read more...

New author Nilav Ghosh brings us a performance tuning article to help your queries run better. This article examines how indexes can help reduce blocking.  Read more...

Finds the largest dupe-sets of one or more columns of a single table or derived table. Great for finding hoggy parameter combinations for perf-testing queries within stored procedures!  Read more...

This article describes different ways of improving the performance of SQL Server queries, with a focus on index optimization.  Read more...

Reports index length stats for indexes who's lengths exceeding parametrized thresholds (defaults to 0 - get all) for total length and seek length, optionally filtering schemas and tables.  Read more...

When creating tables it is difficult to determine exactly how the data will be accessed. Therefore when clustered indexes are chosen they are often just the ID column that makes the row unique. This may be a good choice, but once the application has been used and data access statistics are available you may need to go back and make some adjustments to your tables to ensure your clustered indexes are providing a benefit and not a drain on your applications.   Read more...

I can run the Database Tuning Advisor or examine the query plans, but is there any easier way to determine which indexes may be needed?  Read more...

This article shows how to use the dm_db_index_usage_stats DMV to identify if an Index is being used on not  Read more...

Gets single-column and cumulative-column selectivity stats and @Top largest dupe sets for each cumulative column stepping for a set of one or more columns for a table.  Read more...

Searches database-wide for multiple indexes in the same table which has the same column as the first seek key. Optionally limits to LIKE wildcard patterns of table and schema names.  Read more...

Reports index stats, index size+rows, member seek + include columns as two comma separated output columns, and index usage stats for one or more tables and/or schemas.  Read more...

Lists details for all indexes on one or more tables / schemas, including row count and size. This version outputs the member seek + include columns as two comma separated output columns.  Read more...

Lists details for all indexes on one or more tables / schemas, including row count and size. The non-pivot version also gives data type and other details for the columns.  Read more...

Reports stats on what the query optimizer records in the DMVs as missing indexes and what it says the cost savings will be if they were present. Can limit by table / schema name patterns.  Read more...

Read more...

Indexing a SQL Server database in some respects is considered both an art and a science. Since this is the case, what are some considerations when designing indexes for a new database or an existing one in production? Are these the same types of steps or not? Do any best practices really exist when it comes to indexing? Where does indexing fall in the priority list from an application or production support perspective?  Read more...

Optimize SQL Server non-clustered indexes and queries by considering index fields, compound indexes and SQL Server statistics' impact on non-clustered indexes.  Read more...

Discusses Index Selection impact when functions are wrapped around WHERE clause filtering columns  Read more...