Q.Ms. Zoya is a Production Manager in a factory which packages mineral water. She decides to create a table in a database to keep track of the stock present in the factory. Each record of the table will have the following fields : W_Code – Code of the item (type – CHAR(5)) W_Description – Description of the item (type – VARCHAR(20)) B_Qty – Balance quantity of the item (type – INTEGER) U_Price – Unit Price of the item (type – FLOAT) The name of the table is W_STOCK.

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 …

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. …

Table Creation: The Art of Organising Information

Think of the last time you tried to find a specific contact in your phone. If all your contacts were just listed in one long, unbroken list — no groups, no alphabetical order, no search — you would have to scroll through every single name to find the one you need. That is the problem that table creation solves.

In everyday life, we create tables all the time without thinking about it. A timetable for your classes, a cricket scorecard, a menu with prices — each of these is a table. The instinct to arrange information into rows and columns is natural because it makes comparison and retrieval fast. Table creation, in the context of your studies, is simply the deliberate, systematic act of doing this with data so that it becomes meaningful and usable.

What Exactly Is a Table?

A table is a structured arrangement of data in rows and columns. Each row typically represents one complete record or observation — for example, one student, one month, one product. Each column represents a particular characteristic or variable of that record — for example, name, marks, price, date.

The power of a table lies in its ability to show relationships at a glance. When data is scattered in a paragraph, you have to read and mentally compare. When it is in a table, your eye can move vertically down a column or horizontally across a row, spotting patterns, extremes, and gaps instantly.

The Core Elements of a Table

Every proper table has a few essential parts. Understanding these will help you both read tables and create your own.

• Title: A clear, concise heading that tells the reader what the table contains. It should answer the questions: what, where, and when. For example, "Monthly Sales of ABC Ltd., April–September 2023" is far better than just "Sales Data."
• Column Headings (Captions): These label each column and describe the type of data it holds. They must be precise — "Revenue (in ₹ lakh)" is clearer than just "Revenue."
• Row Headings (Stubs): These label each row, usually on the leftmost column. They identify what each row represents — for instance, the names of months, products, or regions.
• Body of the Table: The actual data cells where numbers or text entries sit. This is the heart of the table.
• Source Note: A line below the table stating where the data came from. This is crucial for credibility, especially in exam answers and project work.
• Footnotes (if needed): Any clarification about a specific entry — for example, an asterisk explaining that a figure is an estimate.

Why Table Creation Matters for You

In your exams and assignments, you will often be asked to present raw data in tabular form. This is not busywork. The examiner wants to see that you can:

1. Identify the key variables in a given set of information.
2. Classify and group data logically.
3. Present it without ambiguity so that anyone reading can understand it immediately.

A well-created table can turn a confusing jumble of numbers into a clear story. For instance, if you are given the population figures of five states over three census years, a table lets you see at once which state grew fastest, which declined, and how each compares to the others. Without the table, you would have to hold all those numbers in your head. …