Skip to main content

Constraints

SQL constraints are rules that enforce limits or conditions on the columns of a table. They ensure data integrity by preventing invalid data from being inserted into the database tables. Let's explore some common SQL constraints with examples:

 

NOT NULL Constraint

The NOT NULL constraint ensures that a column cannot contain NULL values. This is useful for columns where data is required and NULL is not acceptable.

Example:

Suppose we have a table students:

CREATE TABLE students ( student_id INT PRIMARY KEY, student_name VARCHAR(100) NOT NULL, date_of_birth DATE NOT NULL, email VARCHAR(100) );

In this example, student_name and date_of_birth columns cannot be NULL, ensuring every student record has these values.

 

UNIQUE Constraint

The UNIQUE constraint ensures that all values in a column (or a combination of columns) are unique across the table.

Example:

CREATE TABLE users ( user_id INT PRIMARY KEY, username VARCHAR(50) UNIQUE, email VARCHAR(100) UNIQUE );

In this example, Each username and email must be unique across all records in the users table.

 

PRIMARY KEY Constraint

The PRIMARY KEY constraint uniquely identifies each record in a table and ensures that it cannot contain NULL values.

Example:

CREATE TABLE products ( product_id INT PRIMARY KEY, product_name VARCHAR(100), price DECIMAL(10, 2) );

In this example, product_id uniquely identifies each product, and it cannot be NULL.

 

FOREIGN KEY Constraint

The FOREIGN KEY constraint establishes a relationship between two tables. It ensures referential integrity by enforcing a link between the data in the referencing table and the referenced table.

Example:

CREATE TABLE orders ( order_id INT PRIMARY KEY, order_date DATE, customer_id INT, FOREIGN KEY (customer_id) REFERENCES customers(customer_id) );

In this example, customer_id in the orders table is a foreign key that references the customer_id column in the customers table. It ensures that every customer_id in the orders table must exist in the customers table.

 

CHECK Constraint

The CHECK constraint specifies a condition that must be true for each row in a table.

Example:

CREATE TABLE employees ( emp_id INT PRIMARY KEY, emp_name VARCHAR(100), emp_age INT, emp_salary DECIMAL(10, 2), CHECK (emp_age >= 18) );

In this example, CHECK (emp_age >= 18) ensures that the emp_age column must be 18 years or older for every record in the employees table.

 

DEFAULT Constraint

A DEFAULT constraint in SQL is used to specify a default value for a column when no explicit value is specified during an INSERT operation. This ensures that the column always has a value, even if one is not provided explicitly.

Example:

CREATE TABLE employees ( emp_id INT PRIMARY KEY, emp_name VARCHAR(100) NOT NULL, emp_dept VARCHAR(50), emp_salary DECIMAL(10, 2), emp_status VARCHAR(20) DEFAULT 'Active' );

In this example, The employees table has several columns (emp_id, emp_name, emp_dept, emp_salary, emp_status). The emp_status column has a DEFAULT constraint specified as DEFAULT 'Active'.

 

SQL constraints are essential for maintaining data integrity and enforcing business rules within a database. They help ensure that data is accurate, reliable, and consistent, which is crucial for the proper functioning of applications and systems that rely on the database.

Comments

Popular posts from this blog

TechUplift: Elevating Your Expertise in Every Click

  Unlock the potential of data with SQL Fundamental: Master querying, managing, and manipulating databases effortlessly. Empower your database mastery with PL/SQL: Unleash the full potential of Oracle databases through advanced programming and optimization. Unlock the Potential of Programming for Innovation and Efficiency.  Transform raw data into actionable insights effortlessly. Empower Your Data Strategy with Power Dataware: Unleash the Potential of Data for Strategic Insights and Decision Making.

Relationships between tables

In Power BI, relationships between tables are essential for creating accurate and insightful reports. These relationships define how data from different tables interact with each other when performing analyses or creating visualizations. Here's a detailed overview of how relationships between tables work in Power BI: Types of Relationships: One-to-one (1:1):   This is the most common type of relationship in Power BI. It signifies that one record in a table can have multiple related records in another table. For example, each customer can have multiple orders. Many-to-One (N:1):   This relationship type is essentially the reverse of a one-to-many relationship. Many records in one table can correspond to one record in another table. For instance, multiple orders belong to one customer. One-to-Many (1:N):   Power BI doesn't support direct one-to-many relationships.  One record in table can correspond to many records in another table.  Many-to-Many (N:N):  ...

SQL Fundamentals

SQL, or Structured Query Language, is the go-to language for managing relational databases. It allows users to interact with databases to retrieve, manipulate, and control data efficiently. SQL provides a standardized way to define database structures, perform data operations, and ensure data integrity. From querying data to managing access and transactions, SQL is a fundamental tool for anyone working with databases. 1. Basics of SQL Introduction : SQL (Structured Query Language) is used for managing and manipulating relational databases. SQL Syntax : Basic structure of SQL statements (e.g., SELECT, INSERT, UPDATE, DELETE). Data Types : Different types of data that can be stored (e.g., INTEGER, VARCHAR, DATE). 2. SQL Commands DDL (Data Definition Language) : CREATE TABLE : Define new tables. ALTER TABLE : Modify existing tables. DROP TABLE : Delete tables. DML (Data Manipulation Language) : INSERT : Add new records. UPDATE : Modify existing records. DELETE : Remove records. DQL (Da...