How do constraints enforce data integrity in SQL?

Constraints in SQL enforce data integrity by ensuring that the data adheres to defined rules or restrictions.

In SQL, constraints are used to specify the rules concerning the data types in a table. They are used to limit the type of data that can go into a table, ensuring accuracy and reliability of the data. This ensures the integrity of the data. Constraints can be column level, if they apply to a specific column in the table, or table level, if they apply to the whole table.

There are several types of constraints in SQL that help enforce data integrity. The 'NOT NULL' constraint ensures that a column cannot have a NULL value. The 'UNIQUE' constraint ensures that all values in a column are different. The 'PRIMARY KEY' constraint uniquely identifies each record in a table. The 'FOREIGN KEY' constraint prevents actions that would destroy links between tables. The 'CHECK' constraint ensures that all values in a column satisfy certain conditions. Lastly, the 'DEFAULT' constraint provides a default value for a column when none is specified.

For example, if we have a table of students, we might want to ensure that each student has a unique student ID, that no student ID is NULL, and that each student has a valid year of study. We could use the 'PRIMARY KEY' constraint to enforce the uniqueness of student IDs, the 'NOT NULL' constraint to ensure that no student ID is NULL, and the 'CHECK' constraint to ensure that the year of study is within a valid range.

Constraints are a powerful tool in SQL for maintaining data integrity. They allow us to define rules for our data, and SQL will enforce these rules whenever data is added or modified. This helps to prevent errors and inconsistencies in our data, ensuring that our databases are accurate, reliable, and trustworthy.