Use Globally Unique Identifiers in Access and SQL Server

Average Rating: 2.3/5 | Rate this item | 9 users have rated this item.

Use Globally Unique Identifiers in Access and SQL Server (cont'd)

The GUID datatype is here to stay. Its presence in Access and SQL Server makes both products viable systems for the largest of projects, even if most of us never use it. Fortunately, the technology behind the GUID datatype is simple to understand and implement—just being aware of it and its functionality opens the door to easier solutions. Not many database developers hit the 2-billion-record ceiling, but if it could happen to you, design for success with GUIDs.

Previous Page: Randomly Select Rows with GUID Values

Susan Sales Harkins (harkins@iglou.com) is an independent consultant with an expertise in Microsoft Access. SQL: Access to SQL Server, her latest book, was released in January 2002. Currently, Susan writes for a number of publishers including Element K Journals, PC Magazine, builder.com, and DevX.

Arthur Fuller (artful@rogers.com) is an independent consultant who specializes in SQL Server, Microsoft Access, and MySQL. His next book, Special Edition Using MySQL, was published by Que Books in the fall of 2002.

Page 1: Introduction	Page 3: Randomly Select Rows with GUID Values
Page 2: What Do I Need the GUID Datatype For?	Page 4: A Timely Solution