🗄️ SQL Introduction, Relational Models & RDBMS Architecture

📘 1. Core Concept & Architectural Overview

SQL (Structured Query Language) is the universal declarative programming language designed for managing, querying, transforming, and governing structured data stored in Relational Database Management Systems (RDBMS)—such as PostgreSQL, MySQL, SQLite, Oracle, and Microsoft SQL Server.

First introduced by IBM researchers Donald Chamberlin and Raymond Boyce in the early 1970s based on Edgar F. Codd's mathematical Relational Model, SQL is fundamentally declarative: you describe what dataset you need, and the database engine's Query Optimizer figures out the most computationally optimal algorithms (e.g. index seek, hash join, table scan) to retrieve it.

#### The ACID Guarantees:

Production relational databases adhere to ACID properties:

1. 1.Atomicity: All operations in a transaction succeed together or fail together (all-or-nothing).
2. 2.Consistency: Any transaction transitions the database from one valid state to another, strictly enforcing schemas and constraints.
3. 3.Isolation: Concurrent transactions execute without cross-talk or race conditions.
4. 4.Durability: Once a transaction commits, its data survives system crashes and power failures.

---

⚙️ 2. Tables, Rows, Columns & The Relational Schema

• •Database: A container holding schemas, tables, views, and indexes.
• •Table (Relation): A two-dimensional grid of structured data.
• •Column (Field / Attribute): Defines a specific property of fixed data type (e.g., VARCHAR, INT, DECIMAL, BOOLEAN, TIMESTAMP).
• •Row (Record / Tuple): An individual, atomic entity instance in the table.

-- Standard SQL Query Structure
SELECT * FROM Customers;

• •SELECT: Specifies the columns to project in the result set (* denotes all columns).
• •FROM Customers: Identifies the source table to scan.
• •Semicolon (;): The standard SQL statement terminator required across modern database engines.

---

💻 3. Real-World Practical Scenarios

SQL powers the core financial, banking, and logistical backbones of the global digital economy:

• •Banking Ledgers: Recording balance transfers between user wallets where atomicity guarantees zero lost funds.
• •E-Commerce Analytics: Querying product inventories, tracking customer order pipelines, and generating daily sales revenue reports.
• •Web3 Block Explorers: Indexing blockchain blocks, smart contract invocations, and ERC-20 token transfers.

---

💡 4. Best Practices & Pro-Tips

• •Keywords Case Convention: Standard industry SQL convention writes keywords in all-caps (SELECT, FROM, WHERE) and identifiers (table and column names) in snakecase or PascalCase (Customers, `orderdate`).
• •Avoid SELECT * in Production: While SELECT * is convenient for quick interactive exploration, production application queries should always explicitly specify needed columns (SELECT id, name FROM Customers) to prevent unnecessary memory bandwidth and network serialization overhead.

---

💻 Coding Challenge Task

In the test.sql tab:

1. 1.Write a query to select all columns and records from the Customers table:

   SELECT * FROM Customers;

1. 1.Terminate the query with a semicolon ;.
2. 2.Click ▶ Run Code or Submit Solution ✓!

---

📋 Expected Output:

Query Results Table: