Works fine, but the UniqueIdentifier type, with a NewId() default value, has a few advantages. Most importantly, if you replicate data off site and import it into the central repository from other databases, you don't need to worry about key violations. I've run into this problem before with offsite data collections, and the uniqueidentifier type is quite appealing because it is unique across time and space.
Besides, isn't it fun to say "unique across time and space"????!!!
>What is the current view on using identity columns as the primary key for a table?
>
>TIA
The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts. - Bertrand Russell
