Is there any problems with scalability if use uniqueidentifier as a primary key?

Question

0.00/5 (No votes)

See more:

asp.net membership,user databases use uniqueidentifier as a primary key.Is it any problem with scalability for potential million users?

Posted 7-Aug-10 22:36pm

vazg

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

**R. Giskard Reventlov** · Answer 1 · 2010-08-07T22:51:00

Solution 1

See here: Using uniqueidentifier Data[^].

Posted 7-Aug-10 22:51pm

R. Giskard Reventlov

Husain Ahmad Khalid · Answer 2 · 2010-08-08T00:22:00

Solution 2

Because of an offline module in a distributed system We used uniqueidentifier data type as primary key for all tables in our database, and in last 2 years yet we have not received any duplicate value in primary key columns(no conflict).

Thanks

Posted 8-Aug-10 0:22am

Husain Ahmad Khalid

Updated 8-Aug-10 1:07am

v3