Unique key constraint
We use UNIQUE
constraint to enforce uniqueness of a column i.e the column shouldn't allow any
duplicate values. We can add a Unique constraint thru the designer or using a
query.
To add a unique constraint using SQL server management studio designer:
1. Right-click on the table and select Design
2. Right-click on the column, and select Indexes/Keys...
3. Click Add
4. For Columns, select the column name you want to be unique.
5. For Type, choose Unique Key.
6. Click Close, Save the table.
To create the unique key using a query:
Alter Table Table_Name
Add Constraint Constraint_Name Unique(Column_Name)
Both primary key and unique key are used to enforce, the uniqueness of a column. So, when do you choose one over the other?
A table can have, only one primary key. If you want to enforce uniqueness on 2 or more columns, then we use unique key constraint.
What is the difference between Primary key constraint and Unique key constraint? This question is asked very frequently in interviews.
1. A table can have only one primary key, but more than one unique key
2. Primary key does not allow nulls, where as unique key allows one null
To drop the constraint
1. Right click the constraint and delete.
Or
2. Using a query
Alter Table tblPerson
Drop Constraint UQ_tblPerson_Email
To add a unique constraint using SQL server management studio designer:
1. Right-click on the table and select Design
2. Right-click on the column, and select Indexes/Keys...
3. Click Add
4. For Columns, select the column name you want to be unique.
5. For Type, choose Unique Key.
6. Click Close, Save the table.
To create the unique key using a query:
Alter Table Table_Name
Add Constraint Constraint_Name Unique(Column_Name)
Both primary key and unique key are used to enforce, the uniqueness of a column. So, when do you choose one over the other?
A table can have, only one primary key. If you want to enforce uniqueness on 2 or more columns, then we use unique key constraint.
What is the difference between Primary key constraint and Unique key constraint? This question is asked very frequently in interviews.
1. A table can have only one primary key, but more than one unique key
2. Primary key does not allow nulls, where as unique key allows one null
To drop the constraint
1. Right click the constraint and delete.
Or
2. Using a query
Alter Table tblPerson
Drop Constraint UQ_tblPerson_Email
SQL Composite Key
A
composite key is a combination of two or more columns in a table that can be
used to uniquely identify each row in the table when the columns are combined
uniqueness is guaranteed, but when it taken individually it does not guarantee
uniqueness.
Sometimes
more than one attributes are needed to uniquely identify an entity. A primary
key that is made by the combination of more than one attribute is known as a
composite key.
In
other words we can say that:
Composite
key is a key which is the combination of more than one field or column of a
given table. It may be a candidate key or primary key.
Columns
that make up the composite key can be of different data types.
SQL Syntax to specify composite key:
CREATE
TABLE TABLE_NAME
(COLUMN_1,
DATA_TYPE_1,
COLUMN_2,
DATA_TYPE_2,
???
PRIMARY
KEY (COLUMN_1, COLUMN_2, ...));