Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2000-12-18 : 13:58:32
|
Dan writes "We have a design that will have data across databases giving us the need for a unique Identifier (GUID). However, there are lots of places within each database that we need referential integrity/foreign keys and these will be used for joins. In SQL 2000 which is better for the use within a given database? Some on our team feel SQL 2000/Windows is designed using GUIDs so it is optimized for those, yet others feel we should use a GUID only across databases and stick with an int datatype within a given database - use only GUID or both? We will have much heavier usage within a given database and less activity across databases.
The feeling for using the int is that the GUID is too big and heavy for all the joins that are needed and will cause performance problems.
Any thoughts?" |
|
|
|
|
|
Unique Identifier vs int field