If your ID column on a table is a unique identifier (Guid), is there any point creating a clustered primary key on the ID column?
Given that they are globally unique, how would the sorting work?
Share
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.
If your ID column on a table is a unique identifier (Guid), is there any point creating a clustered primary key on the ID column?
Given that they are globally unique, how would the sorting work?
GUIDs as they are are terrible for performance since they are effectively random values (this “breaks” clustered index), and they are awful for indexes, since less entries fit on a single page/extent (SQL Server terms). SQL Server 2005 introduces
newsequentialid()which helps solving first problem.