Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sunsanvin
Master Smack Fu Yak Hacker
1274 Posts |
 Posted - 2008-06-10 : 07:04:52
|
| Dear All,i've observed one particular table, one column is having clustered and non clustered index. is it ok? or i need to drop the non clustered column?the table has 16 columns and at present 8 million records are there. per day approxmately 60000 rows will be getting into the table. it has another 3 non clustered indexes.please suggest me.ArnavEven you learn 1%, Learn it with 100% confidence. |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-06-10 : 07:08:12
|
| Are you sure both indexes have only the column itself and nothing else. If yes, i think you can remove the non clustered index. |
 |
|
|
sunsanvin
Master Smack Fu Yak Hacker
1274 Posts |
Posted - 2008-06-10 : 07:16:30
|
| i'm sure. first column has primary key, so it has clustered index there(i've checked). there is a non clustered index created on the same column.can i drop the non clustered index? are you sure visakh?and one more doubt that is it ok to put a non clustered index on a datetime column?i'm planning to put that because in so many procedures and functions, in WHERE condition we are using that column. is it ok in the matter of performance?ArnavEven you learn 1%, Learn it with 100% confidence. |
|
|
|
|
|
|
non clustered and clustered on same column