UniqueIdentifier to Primary key

Question

1.00/5 (1 vote)

See more:

SQL-Server

How to convert UniqueIdentifier to Primary key integer in

Sql server 2008

Posted 13-Aug-12 0:01am

sachin hanchate

Add a Solution

Comments

bbirajdar 13-Aug-12 6:06am

Why do you need it ?

3 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)

codeBegin · Answer 1 · 2012-08-13T00:07:00

Solution 2

Uniqueidentifier Column as Primary Key, a worst choice[^]

Posted 13-Aug-12 0:07am

codeBegin

StianSandberg · Answer 2 · 2012-08-13T00:06:00

Solution 1

UniqueIdentifier is a Guid and cannot be convertet to an int. But if you add a new column INT and set it as primary key and is identity the database will give all rows a new id (int) And you can keep you UniqueIdentifier column or just delete it.. (unless it has a lot of relations...)

Posted 13-Aug-12 0:06am

StianSandberg

Wendelius · Answer 3 · 2012-08-13T00:39:00

Uniqueidentifier is used to generate a surrogate key[^] and it contains both characters and numbers so it cannot be converted to any number data type.

If you want to convert it to something, you can use character datatypes, for example nvarchar. However, you normally shouldn't need to convert it to anything special since the only purpose of unique identifier is to identify a single record.

If you're looking for the .Net equivalent data type for parameters, you can use SqlDbType.UniqueIdentifier. See: SqlDbType Enumeration[^]

In my opinion keeping the primary key as an uniqueidentifier is an excellent choice, especially if replication is involved.