Sqlserver logical design problem

Question

0.00/5 (No votes)

See more:

Hi.

I intend to design a form by Asp.net that employees insert their personal information , and then these data to be stored in DB(Sqlserver 2008r2).

in my DB logical design , i had supposed to be:(PersonelCode,Int, pk,unique,not null)
but my problem is : someone told me that PersonelCode datatype shouldn't be Int, because some of them include words, or begin from Zero(example: 0343),
so what shall i do , is it correct to change the datatype to String ? if yes , how can keep it unique and to specify person's identificaion?

Posted 25-Jul-12 20:36pm

mohammad ehsan

Add a Solution

Comments

dimpledevani 26-Jul-12 2:44am

It is not necessary, every company or firm have their own way of storing such data

mohammad ehsan 26-Jul-12 3:22am

i didn't get exactly what you mean?
personelCode can not be either int and string ,if so , it can not be unique and can not be realted to other tables>

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)

Nilesh Rokade · Answer 1 · 2012-07-25T23:09:00

Solution 1

Keep it as string ..before insertion check in insertion procedure if it is already exists...otherwise it will throw sql exception...you will have flexibility in implementing if you use string since it is easy to manage than int for e.g. compare ,use in search like patterns....

Posted 25-Jul-12 23:09pm

Nilesh Rokade