Q.Nisha is assigned the task of maintaining the staff data of an organization. She has to store the details of the staff in the SQL table named EMPLOYEES with attributes as EMPNO, NAME, DEPARTMENT, BASICSAL to store Employee's Identification Number, Name, Department and Basic Salary respectively. There can be two or more Employees with the same name in the organization.

Primary Key Identification

Think about how you tell two students apart in a classroom. If you call out "Rahul," there might be three Rahul's. But if you say "Rahul Sharma, roll number 12," you've pointed to exactly one person. That unique identifier — the roll number — is doing the job of a primary key.

The Everyday Intuition

Every collection of things needs a way to refer to each item without confusion. In a library, every book has a unique accession number. In a bank, every account has an account number. In a school, every student has a unique admission number. These are not random — they are deliberately chosen so that no two items share the same identifier.

This is the core idea: a primary key is a single attribute (or a combination of attributes) that uniquely identifies each record in a table. No two rows can have the same primary key value, and no primary key can be empty (null).

The Precise Meaning

In database terms, a primary key serves two non-negotiable rules:

• Uniqueness — every value in the primary key column must be different from every other value. If you have 100 students, you need 100 distinct roll numbers.
• Non-null — every record must have a primary key value. You cannot have a student with "no roll number."

A primary key can be a single column, like a student ID. Or it can be a composite key — two or more columns taken together to create uniqueness. For example, in a table recording which books students have borrowed, neither "Student ID" alone nor "Book ID" alone is unique (a student borrows many books; a book is borrowed by many students over time). But the combination of "Student ID + Book ID + Date Borrowed" together can be unique.

Why It Matters

Without a primary key, you cannot reliably update or delete a specific record. Imagine a school database where two students have the same name "Ananya Sharma." If you try to delete "Ananya Sharma," the database has no way to know which one you mean. With a primary key, you say "delete student with roll number 45" — and it's unambiguous. …

Unique Not Null: A Concept-First Explanation

Think about your Aadhaar number. Every citizen gets exactly one, and no two people share the same number. But here's the catch — you must have one. You cannot leave that field blank. That is the essence of Unique Not Null.

The Everyday Intuition

Imagine you are maintaining a class register. You want to record each student's roll number. Two things are obvious: every student must have a roll number (you cannot leave it empty), and no two students can share the same roll number. That is a Unique Not Null constraint in action.

Now contrast this with a student's phone number. Some students may not have one — that field can be left blank. And two siblings in the same class might share a phone number. So phone number is neither unique nor mandatory. The difference is intuitive once you see it.

The Precise Meaning

Unique means that within a given column (or set of columns), every value must be distinct from every other value. No duplicates allowed. Not Null means that the column cannot be left empty — it must contain a value. When you combine the two, you get a column where:

• Every row must have a value (no blanks)
• Every value must be different from every other value in that column

Why It Matters

In real-world data, certain pieces of information are both mandatory and naturally unique. Consider these examples:

• Employee ID in a company database: every employee must have one, and no two employees can share the same ID
• PAN Card number in a tax database: mandatory for taxpayers, and unique by law
• Email address in a user registration system: every user must provide one, and no two accounts can share the same email

If you allowed duplicates in such columns, you would create confusion — two employees with the same ID, or two taxpayers with the same PAN. If you allowed blanks, you would have records that cannot be identified at all. …

SQL Table Creation: A First Look

Think of a table as a structured list — the kind you might keep on paper for something you track regularly. A teacher might have a class register: columns for Roll Number, Student Name, and Attendance, with each row being one student's record. That register is a table. SQL (Structured Query Language) is just the language we use to create and manage such tables inside a computer database.

The core idea is simple: a table organises data into rows (records) and columns (fields). Each column holds one type of information — names, dates, amounts — and every row is one complete entry. When you create a table, you are essentially drawing the empty grid and labelling each column with its name and the kind of data it will hold.

The CREATE TABLE Statement

To build a table, you use the CREATE TABLE command. It tells the database: "Make a new empty table with this name and these columns." The basic structure looks like this:

CREATE TABLE table_name (
    column1 datatype,
    column2 datatype,
    column3 datatype
);

You replace table_name with whatever you want to call your table (like Students or Orders). Inside the parentheses, you list each column, followed by its datatype — the kind of data that column will store.

Choosing Datatypes

Every column must have a datatype. This is not a formula or calculation; it is simply a rule that tells the database what sort of information goes in that column. Common datatypes include:

• INT — for whole numbers (like Roll Number or Age)
• VARCHAR(n) — for text of variable length up to n characters (like Name or Address)
• DATE — for dates (like Date of Birth)
• DECIMAL(p,s) — for numbers with decimal places (like Price or Salary)

A Simple Example

Suppose you want to create a table to store information about books in a library. You might write:

CREATE TABLE Books (
    BookID INT,
    Title VARCHAR(100),
    Author VARCHAR(50),
    PublishedYear INT,
    Price DECIMAL(6,2)
);

This creates a table called Books with five columns. BookID will hold whole numbers, Title and Author will hold text (up to 100 and 50 characters respectively), PublishedYear will hold whole numbers, and Price will hold numbers with up to two decimal places. The table is empty — it has no rows yet — but it is ready to accept data.

Why Table Creation Matters …