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
- Clean your room
- Tim Lake, Algonquin
- SQL Server 2005 file sizes and filegrowth
- Junior Rangers
- Georgian Manor, hard sells and pyramid schemes
- Deciding against Code Collapse in SQL Server Management Studio 2008
- Improved SQL Server Index Scripting from Excel
- SQL Server Performance and the IN clause
Tag! You’re it!
- climate change
- environmental awareness
- graphic novel
- Guelph Festival of Moving Media
- Guelph International Film Festival
- Jane Austen
- long distance
- Old Growth Forest
- Robert J. Sawyer
- science fiction
- short story
- Space opera
- speculative fiction
- SQL Server
- SQL Server 2005
- Stephen King
- The Education of Mike Moonblazer