Q.Observe the following tables, EMPLOYEES and DEPARTMENT carefully and answer the questions that follow: TABLE : EMPLOYEES ENO ENAME DOJ DNO E1 NUSRAT 2001-11-21 D3 E2 KABIR 2005-10-25 D1 TABLE : DEPARTMENT DNO DNAME D1 ACCOUNTS D2 HR D3 ADMIN

Database Fundamentals

Think of a database as a well-organised filing cabinet. In your daily life, you already manage small databases without realising it — your phone's contact list, the catalogue of a library, or even the list of students in a class register. Each of these is a collection of related information stored in a structured way so that you can find what you need quickly.

What Exactly Is a Database?

A database is a collection of related data that is stored and managed systematically. The key word here is related. A random pile of papers on a desk is not a database — but the same papers, sorted into folders with labels and a clear order, become one. The purpose of a database is to allow efficient storage, retrieval, modification, and deletion of data.

Why Do We Need Databases?

Imagine a small business that keeps customer orders in a notebook. As the business grows, the notebook becomes impossible to manage — pages get lost, two customers might be given the same order number, and finding a specific order takes forever. A database solves all these problems.

Databases provide:

• Centralised control — all data lives in one place, so everyone works with the same information
• Data consistency — rules can be enforced (for example, an order must belong to a real customer)
• Security — different users can be given different levels of access
• Reduced redundancy — the same piece of information is not stored in multiple places unnecessarily
• Data independence — the way data is stored can change without affecting how users view it

The Core Idea: Tables and Relationships

The most common type of database is the relational database. Think of it as a collection of tables, where each table stores information about one kind of thing.

A table is made up of rows and columns. Each column represents a field (a single piece of information, like a name or a date), and each row represents a record (one complete set of fields, like one customer's full details).

For example, a university might have a Student table with columns: Roll Number, Name, Date of Birth, and Course. Each row is one student.

The real power comes from relationships between tables. The same university might have a Course table and an Enrolment table. The Enrolment table links a student to a course using the student's roll number and the course code — without repeating all the student's details or all the course details. This is what makes a database efficient.

Database Management System (DBMS)

A Database Management System is the software that lets you create, manage, and interact with a database. You do not directly touch the data files — the DBMS does that for you. Popular examples include MySQL, Oracle, and Microsoft Access.

The DBMS handles:

• Data storage and retrieval — it decides how to physically store data on a disk
• Query processing — when you ask for "all students born after 2005", the DBMS finds the answer …

Relational Algebra Operations: A First Look

Think of a relational database as a collection of neat, rectangular tables. Each table has rows (records) and columns (attributes). Now, suppose you want to ask questions of this data — "Which customers live in Delhi?" or "Show me all orders placed last month." Relational algebra is the set of basic operations you use to answer such questions. It is the language of queries at the most fundamental level.

You do not need to write code or do math. You only need to understand what each operation does to a table — like a set of tools in a toolbox.

The Core Operations

There are eight classic operations. They fall into two groups: those that work on one table at a time, and those that combine two tables.

Operations on a Single Table

Select (also called Restrict) — This operation picks certain rows from a table based on a condition. For example, from a table of students, you might select only those rows where the city is "Mumbai". The result is a smaller table with the same columns but fewer rows.

Project — This operation picks certain columns from a table. For example, from a student table with columns Roll No, Name, City, and Marks, you might project only Name and City. The result is a table with fewer columns. Duplicate rows are automatically removed.

Rename — This operation simply gives a new name to the resulting table or to its columns. It is useful when you need to refer to the same table more than once in a query, or when you want clearer column headings.

Operations That Combine Two Tables

Union — This combines two tables that have the same structure (same number of columns and compatible data types). The result contains all rows that appear in either table, with duplicates removed. Think of it as "add the rows of one table to the rows of another, but keep only unique ones."

Set Difference — This gives you rows that are in the first table but not in the second. For example, "Which students are enrolled in Course A but not in Course B?"

Intersection — This gives you rows that appear in both tables. For example, "Which customers have bought both a laptop and a printer?"

Cartesian Product — This pairs every row of the first table with every row of the second table. If the first table has 10 rows and the second has 5, the result has 50 rows. This operation is rarely used alone — it is the foundation for the most powerful operation of all.

Join — This is the heart of relational algebra. A join combines rows from two tables based on a related column between them. For example, you have a Customers table and an Orders table. The join operation matches each order to the customer who placed it, using the Customer ID column that appears in both tables. The result is a single table with all the customer details alongside their orders.

Why Relational Algebra Matters …