Lynn Pettis (8/22/2014)
Eirikur Eiriksson (8/22/2014)
Lynn Pettis (8/22/2014)
Even if you use a natural key as the primary key, I would still consider adding a synthetic id to the tables and making it a non nullable unique index on the table. I can't tell you how many times a primary key value (single or multiple column) suddenly was no longer a good candidate as a primary key for a table due to changing requirements. Having an alternate key readily available has helped me on numerous occasions.Further on this, it guaranties an ever increasing order of values, hence preventing fragmentation/page splitting on inserts.
😎
If you make the SID the clustered index. Not necessarily the best choice for the clustered index on a table. You really need to analyze the various data access paths before choosing the best index for your clustered index.
Quite true. One of the stronger cases for using SID as a clustered index is when either an ever increasing order of values cannot be guaranteed or achieved.
😎