First, thank you for your ok (I am not saying this facetiously; I trust you and others' expertise on this topic).
Yes, I know (read about it) that clustered index is like "sort" in VFP. And when I changed the PK from the non-clustered to clustered (on a sample table of about 500,000 rows), it took about 3-4 minutes to process. SQL Server - if I understand it correctly - had to build this clustered index and then create/update all non-clustered indexes.
>Based on that, you *should be* ok to make it a clustered index. One thing I haven't seen mentioned here. A clustered index is really a physical storing of the data in index order. You can insert, but it could mean rewriting a large portion of data.
>
>>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.
"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
