Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
For me there is no need/intention to create multiple index names for a same column. When i’m studying about index i tried the following test. What is the use of the same? Is there any feature?
What i have tried is:
create index id on TestIndex(EmployeeMumber) create index id1 on TestIndex(EmployeeMumber) create index id2 on TestIndex(EmployeeMumber)
The result is: Command(s) completed successfully.
Thanks
SQL Server doesn’t prevent you from creating duplicate indexes (though there has been an unsuccessful push to change this). The “won’t fix” is probably largely for backward compatibility reasons – there were probably use cases in previous versions where people would create a new index before dropping an old one, back when options like
DROP_EXISTINGor rebuilding online didn’t exist. As new features in the engine evolve, such asINCLUDEcolumns, filtered indexes, etc. it is also more complex to determine whether or not two indexes are, in fact, duplicates.