Sql server Identity usage

Can I make an Identity column in a table a primary key plus make its associated tables have a primary key/Foreign that is an identity also?
If so, can I cascade delete or cascade update on an identity column?
Lawrence AverySystem DeveloperAsked:
Who is Participating?
 
chaauConnect With a Mentor Commented:
In short: Yes for all (except for #2 - see below).

In details:
1. You can make the identity column a primary key. Make sure that it has a property to not allow NULLS

2. You create a columns in associated tables with their own primary keys. The primary key in the associated table can be an identity column. However, I do not believe you should make it a foreign key to your main table, because in this case the associated table will be in a one-to-one relationship to your main table. Imagine this simple schema:

Table Patient:
PatientID INT NOT NULL IDENTITY(1,1) PRIMARY KEY
Name Varchar(100)
Address Varchar(100)

Table PatientPhones
PhoneID INT NOT NULL IDENTITY(1,1) PRIMARY KEY
PatientID INT
Phone Varchar(20)
Type CHAR(1)

If a patient has many phones (Home, Mobile, Work, etc) you can just add more records to the PatientPhones table. The PhoneID key in this table will ensure uniqueness. The foreign key should only include the PatientID. You can make it cascading.

3. You can make the column cascading. However, please note that if you want to update an IDENTITY column in your main table you need to jump a few hoops. In short, you need to use set identity_insert Patient ON statement. But it is a question out of scope of your questions. Please let me know if you want to explore this
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.