The Cost of GUIDs as Primary Keys

By Bill Graziano on 8 January 2005 | 2 Comments | Tags: Data Types, Indexes


Kristen submitted "In this article, Jimmy Nilsson presents the pros and cons of using globally unique identifiers (GUIDs) as the datatype for primary keys in SQL Server 2000. In doing so, he shows you test results that hint of performance characteristics and introduces you to a special type of GUID that he invented, called COMBs, that solves what otherwise might give you a big throughput problem.

He also point out that GUIDs are not guaranteed to be 'Globally Unique'"
Follow the link to The Cost of GUIDs as Primary Keys...

Discuss this article: 2 Comments so far. Print this Article.

If you like this article you can sign up for our weekly newsletter. There's an opt-out link at the bottom of each newsletter so it's easy to unsubscribe at any time.

Email Address:

Related Articles

Using the TIME data type in SQL Server 2008 (6 March 2008)

Using Included Columns in SQL Server 2005 (14 January 2008)

Using the DATE data type in SQL Server 2008 (6 December 2007)

SQL Server Indexes: The Basics (26 November 2007)

Working with Time Spans and Durations in SQL Server (15 October 2007)

DATEDIFF Function Demystified (20 March 2007)

Using Indexed Computed Columns to Improve Performance (16 January 2007)

Microsoft SQL Server 2000 Index Defragmentation Best Practices (2 May 2004)

Other Recent Forum Posts

Stored Procedure to Insert records into Next row (0 Replies)

Where clase - column name as parameter (5 Replies)

Trigger Error (1 Reply)

Stored procedure out parameter error (6 Replies)

Pivot Transformation (0 Replies)

SPROC paging and sorting issue (3 Replies)

how to do this? (8 Replies)

Running a Date Variable on One Field (6 Replies)

Subscribe to SQLTeam.com

Weekly SQL Server newsletter with articles, forum posts, and blog posts via email. Subscribers receive our white paper with performance tips for developers.

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -