Reasons Why You May Not Want to Use a Heap

For a book project I am working on, I have started compiling a list of reasons why heaps aren't usually a good choice when designing a database. Now, I didn't say that heaps are always bad, but in most cases, I think they should be avoided so pleae read the list to see why.

SQL 2008 Indexes

Obtaining Index Usage Information

This article shows how the sys.dm_db_index_usage_stats DMV can be used to tune your indexes, and maximize the performance of your database

Finding a better candidate for your clustered indexes

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.

Indexes

SQL Server Index Basics

Given the fundamental importance of indexes in databases, it always comes as a surprise how often the proper design of indexes is neglected. It often turns out that the programmer understands detail, but not the broad picture of what indexes do. Bob Sheldon comes to the rescue with a simple guide that serves either to remind or educate us all!

Finding Execution Time of a SQL Statement

Capturing the execution time for rebuilding an index for set of tables.

Are Your Indexes Being Used Effectively?

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

Included index

Predictable Index Fragmentation

This technical article provides an overview of how to produce specific levels of index fragmentation. Useful for creating test plans.