Re: uniqueidentifier datatype
- From: "TheSQLGuru" <kgboles@xxxxxxxxxxxxx>
- Date: Fri, 23 Oct 2009 13:27:51 -0500
avoid uniqueidentifiers at all costs if there is any other alternative
(including compound keys). 16 bytes is a lot and fragmentation can be
horrific as well.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Jack" <jack@xxxxxxxxxxxx> wrote in message
news:ayhEm.13998$6q1.11726@xxxxxxxxxxxxxxx
I've got a co-worker who wants to use the uniqueidentifier datatype as a
means to identify a record containing sensitive information. This GUID
would be used in a website cookie. The twist is he also then wants to use
the guid in other tables to create the relationships by defining the
foreign table columns as a uniqueidentifier datatype too.
I think this is a little nuts. My understanding of the uniqueidentifier
datatype is it's generally used for replication, not to defined key
relationships between tables. Can you please give me some best practices
for this datatype and maybe some alternatives I can suggest?
Thank you.
.
- References:
- uniqueidentifier datatype
- From: Jack
- uniqueidentifier datatype
- Prev by Date: Re: exec master.dbo.xp_ versus exec master..xp_
- Next by Date: Re: how to transfer tables from one database to another database?
- Previous by thread: Re: uniqueidentifier datatype
- Next by thread: Improve search statement with '%'
- Index(es):
Relevant Pages
|
