The right index in the right place can really up your database performance. But applying too many indices can lead to a very nasty overhead problem. So how do you learn where to spend your index resources where they’re most needed?
Knowing your database schema is crucial but a complex database can make deciding where to put your index a very difficult task.
An article by Ian Stirk in January’s MSDN magazine really helped me. The brilliant code and my knowledge of the schema helped pinpoint places where I should put indices. Look, especially, at STEP04 [Identify the missing (or incomplete indexes) (TOP 20), for ALL databases].
If wishes were horses
Golbing Time Dimension
- Laurier in Chain e-mails on Immigration
- Using Excel to generate Inserts for SQL Server
- Junior Rangers
- Georgian Manor, hard sells and pyramid schemes
- A True Love Haiku
- SP (Stored Procedure) Audit script for SQL Server 2005
- SQL Server 2005 file sizes and filegrowth
- Morals on the loose
- Christmas has come surly
- Databases are an Essential Art
Tag! You’re it!2008 age Apocalypse art Atheism bicycling Biology book Canadian cards Christmas comedy conservation cycling database Disney documentary environment environmental awareness Excel fantasy film game global warming graphic novel Guelph Guelph Festival of Moving Media Guelph International Film Festival haiku hiking history humour Jane Austen long distance love Microsoft Montreal movie music mystery native Nature Neil Gaiman novel Old Growth Forest Oshawa performance philosophy Poem poetry Poetry Month quote recipe relationship review Robert J. Sawyer science fiction short story silliness silly snow society Space opera speculative fiction Spring SQL SQL Server SQL Server 2005 Stephen King story The Education of Mike Moonblazer touring TV water writing