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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-07-27 : 10:17:40
|
| Surbhi writes "One column 'COL1' is defined as Primary key in A1 table, hence one clustered Index.But after some time I see nonclustered, auto created Indexes on columns where I had not defined any index like _WA_Sys_COL2_5CD6CB2B_WA_Sys_COL3_5CD6CB2B_WA_Sys_COL4_5CD6CB2B _WA_Sys_COL5_5CD6CB2B_WA_Sys_COL6_5CD6CB2B_WA_Sys_COL7_5CD6CB2B _WA_Sys_COL8_5CD6CB2B _WA_Sys_COL9_5CD6CB2B _WA_Sys_COL10_5CD6CB2B With Index_Description"nonclustered, statistics, auto create located on PRIMARY" If I try to drop these indexes, then I get the message"Cannot drop the index 'A1._WA_Sys_COL2_5CD6CB2B', because it does not exist in the system catalog."And if I see in SysIndexes Table then I get the same Index.Pl. tell me in detail about the Auto Created NonClustered Indexes? How to drop these indexes? Reasons of the creation of the same and impact of such type of indexes on performance!!" |
|
|
|
|
|
nonclustered, auto create Index