Constraints -- Sql Server

     Constraints are the rules enforced on data columns on table. These are used to limit the type of data that can go into a table. This ensures the accuracy and reliability of the data in the database.

    Constraints could be column level or table level. Column level constraints are applied only to one column, whereas table level constraints are applied to the whole table.

    Constraints can be specified when a table is created with the CREATE TABLE statement or you can use ALTER TABLE statement to create constraints even after the table is created.

Dropping Constraints:

   Any constraint that you have defined can be dropped using the ALTER TABLE command with the DROP CONSTRAINT option.

  For example, to drop the primary key constraint in the EMPLOYEES table, you can use the following command:

  ALTER TABLE EMPLOYEES DROP CONSTRAINT EMPLOYEES_PK;

   Some implementations may provide shortcuts for dropping certain constraints. For example, to drop the primary key constraint for a table in Oracle, you can use the following command:

ALTER TABLE EMPLOYEES DROP PRIMARY KEY;

   Some implementations allow you to disable constraints. Instead of permanently dropping a constraint from the database, you may want to temporarily disable the constraint and then enable it later.

Integrity Constraints:

     Integrity constraints are used to ensure accuracy and consistency of data in a relational database. Data integrity is handled in a relational database through the concept of referential integrity.

     There are many types of integrity constraints that play a role in referential integrity (RI). These constraints include Primary Key, Foreign Key, Unique Constraints and other constraints mentioned above.