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
- Using Excel to generate Inserts for SQL Server
- Georgian Manor, hard sells and pyramid schemes
- Laurier in Chain e-mails on Immigration
- Ancho and Chipotle
- SQL Server 2005 file sizes and filegrowth
- Multiple File Renaming in Ubuntu
- Data Obfuscation through Random String replacement in SQL Server
- First and Last Date of Month in T-SQL
- Junior Rangers
- About the Golber
Tag! You’re it!2008 age Apocalypse art backup bicycling Biology book Canadian cards Christmas comedy concert conservation cycling database Disney documentary environment environmental awareness Excel fantasy film game global warming graphic novel graphic novels Guelph Guelph Festival of Moving Media Guelph Field Naturalists Guelph International Film Festival haiku hiking history humour Jane Austen Kazu Kibuishi long distance love Microsoft Montreal movie music mystery native Nature Neil Gaiman novel Old Growth Forest Oshawa performance podcast Poem poetry quote recipe review Robert J. Sawyer science fiction short story silly Space opera speculative fiction Spring SQL SQL Server SQL Server 2005 Stephen King story The Education of Mike Moonblazer touring TV water writing WWW