Q.The ABC Company is considering to maintain their salespersons records using SQL to store data. As a database administrator, Alia created the table Salesperson and also entered the data of 5 Salespersons. Table : Salesperson S_ID S_NAME AGE S_AMOUNT REGION S001 SHYAM 35 20000 NORTH S002 RISHABH 30 25000 EAST S003 SUNIL 29 21000 NORTH S004 RAHIL 39 22000 WEST S005 AMIT 40 23000 EAST Based on the data given above, answer the following questions :

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

Database Querying: Asking Questions of a Data Collection

Think of a library. You walk in, and instead of wandering through endless shelves, you go to the librarian and say: "I need all books by R. K. Narayan published after 1980." The librarian knows exactly where to look, finds the relevant books, and hands you a short list. That act of asking — of specifying exactly what you want from a large, organised collection — is the essence of querying.

A database is like that library, but for digital information. It stores data in a structured way, typically in tables with rows and columns. A query is simply a question you ask of that database. You don't need to know where the data lives or how it's stored internally. You just need to state what you want.

The Precise Meaning

In formal terms, a database query is a request for data or information from a database. The request is written in a special language that the database understands. The most common such language is SQL (Structured Query Language), but the concept of querying exists in every database system.

When you query a database, you are doing one of four things:

• Retrieving data (the most common — "show me the customers who live in Delhi")
• Inserting new data ("add this new student record")
• Updating existing data ("change this address")
• Deleting data ("remove this old order")

For a commerce or humanities student, the retrieval part is where the real power lies. You are not just pulling out raw data — you are filtering, sorting, and combining it to get answers.

Why It Matters

A database without querying is like a library with the lights off. The data exists, but you cannot use it. Querying turns stored facts into actionable information.

Consider a small business owner who keeps customer records in a spreadsheet. Without querying, they might scroll through hundreds of rows to find customers who haven't purchased in six months. With a query, they type one request and get the answer instantly. That answer might lead to a targeted marketing campaign, which brings in revenue.

The Intuition Behind It

Every query has a simple structure at its core:

1. What data do you want? (Which columns or fields?)
2. Where is it? (Which table or collection?)
3. Under what conditions? (Which rows match your criteria?)

If you can answer those three questions in plain English, you are already thinking like someone who queries databases. The technical language (SQL) is just a way to write those answers down so the computer understands.

A Real-World Example …