How to add a 16 digit auto incremental field in sql?

Question

0.00/5 (No votes)

See more:

SQL-Server-2008

, +

How to add a 16 digit auto incremental field in sql? I would like to create an application in vc 2010 which has 3 fields, name, date of birth and pincode. If user gives all the information including the pin code, it should be inserted in the database. But the unique id field will be updated automatically with the pincode (6 digit)+ 16 digit.. For instance, if the user gives the pincode as 641001 then, it should be added as 6410010000000001, and if another user with same pin code enters the details, then it should be added as 6410010000000002. And if another user with different pincode 552145 then it should be added as 5521450000000001.. and so on.. It should check for pincode if already exists, then add 1 to the last digit and update it. and it should be unique.

Posted 28-Feb-13 2:01am

Gokulnath007

Add a Solution

1 solution

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)

phil.o · Answer 1 · 2013-02-28T02:12:00

I don't recommend to do that (trying to put several informations in your primary field).

Why don't you use a simple integer primary key, and store your pincode/rank in another column ?

The goal of a primary key is to identify a unique record without ambiguity ; trying to put more informations in it will give you more problems than it will solve.

Plus, primary keys are indexed ; if you use a large value as a primary key, you will suffer huge performance losses due to maintenance of index.

So I'm not going to give a solution to your problem the way you have analyzed it. You should review your design and stick to well-known good practices regarding database design.