The ID is an Identity column. If a user creates an order it is (ID) automatically set to the next ID sequential number. If user does not save the newly created record, the "missed" number will never be inserted.
>Just to make sure about this before you do it. The clustered index will be an integer and always sequential? Say for some reason ID 302 gets skipped, Will a new 302 ever get inserted?
>
>
>>I am really a dunce when it comes to understanding how SQL Server works. But the PK is integer and from what you are saying 'no downsides'. Now I will be connecting to all my customers and one-by-one changing this PK constraint to clustered.
>>Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
