Click here to Skip to main content
15,843,325 members

Comments by YSLGuru (Top 1 by date)

YSLGuru 3-Oct-11 13:58pm View    
Deleted
No offense intended but your wrong about this being a great PK. Here is a post by Microsoft employee Umachandar Jayachandran (works on the SQL Team) on the subject where he details why you shouldn’t consider a GUID for this kind of scenario. Thats not to say you would never use a GUID but that you need to understand the pros and cons of using it so you know when to and when not to use it and in the scenario the poster describes the GUID is NOT the better choice.

For the record – I manage databases with row counts in the hundreds of millions of rows so I have a little bit of experience working with keys and I have yet to see where we’d be better off with a 36 digit alphanumeric key then a standard incrementing numeric only key.

http://social.msdn.microsoft.com/forums/en-US/transactsql/thread/e77fef16-a697-4bf9-affd-8189957a4d63/