GUIDs keys are pretty common for situations where you need to merge similar data from multiple sources.
Imagine several identical systems running in parallel in separate parts of the country. Odds are you'll want to consolidate all that data to a central data warehouse eventually. When you merge them together, If all those databases were using numeric keys, now you've got duplicate keys. No good. If you used GUIDs for keys then you wouldn't have the problem.
There are other somewhat similar situations where GUID keys are useful too.
--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net
I have one questoin... and i am not trying to start a flame or anythning..
But why would you use a GUID as the primary key? what is wrong with ints or numeric or things that sql knows how to index properly.
I used .NET to generate a GUID for creating a new record in Access DB as primary key. Is it guaratee to be unique in the DB as the GUID is not generate in DB?? If so, is that mean GUID is generated based on machine instead of application, right??
Million Thanks