Click here to Skip to main content
Rate this: bad
good
Please Sign up or sign in to vote.
I am using Tuning Adviser to suggest indexes. I am not sure should I make all suggested indexes (many are non-clustered). I am afraid that I will do the opposite (degradation) by using so many indexes. Any suggestions ?
Posted 16-May-13 19:20pm
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 1

By definition there can only be one clustered index per table, as that defines the physical order of records. You generally don't want to define a clustered index on a field that doesn't constantly increase (like an autonumber field), as any insert into the middle of the values would result in the physical reordering of records in that table.
 
If you are having specific performance issues, consider implementing some of the recommended indices - I have used the Tuning Adviser successfully in the past. YMMV.
  Permalink  
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 2

Before creating indexes to optimize your database you need to be sure how to use indexes. You need to locate frequently used queries and then you can start creating indexes ...
Please read this - SQL Server Performance Tips and Guidelines[^]
  Permalink  

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
0 BillWoodruff 360
1 Mathew Soji 309
2 DamithSL 225
3 Afzaal Ahmad Zeeshan 202
4 Maciej Los 190
0 OriginalGriff 6,249
1 Sergey Alexandrovich Kryukov 5,853
2 DamithSL 5,183
3 Manas Bhardwaj 4,673
4 Maciej Los 3,865


Advertise | Privacy | Mobile
Web03 | 2.8.1411019.1 | Last Updated 20 May 2013
Copyright © CodeProject, 1999-2014
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100