January 3, 2012 at 10:26 am
Should it just be a varchar(100)?
January 3, 2012 at 10:28 am
uniqueIdentifier?
January 3, 2012 at 10:48 am
Yeah, uniqueIdentifier is what you're looking for. I generally try to avoid them but I'm sure they have their uses.
January 3, 2012 at 12:08 pm
bwoulfe (1/3/2012)
Yeah, uniqueIdentifier is what you're looking for. I generally try to avoid them but I'm sure they have their uses.
+1
Choosing the correct datatype does matter !
Just keep in mind you may be wasting space if there is a better alternative .
http://www.sqlskills.com/BLOGS/KIMBERLY/category/GUIDs.aspx
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 4, 2012 at 4:48 am
My recommendation is that, while UniqueIdentifier and GUIDs certainly have their good uses, they should probably never be used as a Clustered Index. Further, yes, they can be used as a PK, but if it's not really needed to maintain "uniqueness" across multiple servers or some such, I'd avoid the use of GUIDs for all the reasons found in the link to Kimberly Tripp's article that ALZDBA provided a link to, and more.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply