| Main Idea | Explanation | Examples | Key Terms |
|---|---|---|---|
| Definition | DBMS manages data as files. RDBMS organizes data into related tables. | DBMS: XML, MS AccessRDBMS: MySQL, Oracle | Database, Relational Database |
| Data Structure | Data is stored as files or objects. | File-based systems | Files, Hierarchies |
| Data is stored in structured tables with rows and columns. | MySQL, PostgreSQL | Tables, Rows, Columns, Schema | |
| Relationships | No support for data relationships (no keys). | Separate files | Relationships not enforced |
| Supports relationships with keys (primary/foreign keys). | Employee-Department in SQL | Primary Key, Foreign Key | |
| Data Integrity | Does not guarantee integrity constraints like uniqueness. | Manual checks required | Data Integrity, Validation Rules |
Enforces data integrity using constraints (like NOT NULL). | UNIQUE, PRIMARY KEY constraints | Constraints, ACID | |
| Data Accessibility | Accessing data requires complex custom queries or manual work. | Manually navigating files | Low Scalability |
| Data is accessible with SQL queries, making it easier and faster. | SELECT * FROM table_name; | SQL, Query | |
| Multi-User Support | Limited multi-user support or requires manual effort to avoid conflicts. | Single-user systems like MS Access | Concurrency |
| Handles multiple users efficiently with transaction support. | Bank databases with many users | Transaction, Concurrency Control | |
| Scalability | Less scalable for large datasets or complex applications. | Personal data systems | Scalability, Performance |
| Highly scalable for large, dynamic applications. | E-commerce, social media | Horizontal Scaling | |
| ACID Compliance | Lacks ACID compliance (Atomicity, Consistency, Isolation, Durability). | No automatic rollback or recovery | ACID |
| Fully ACID-compliant, ensuring reliable transactions. | Banking systems | Transactions, Durability | |
| Security | Basic security features like user authentication. | File-level access controls | Authentication |
| Advanced security features like roles, privileges, and encryption. | Database roles, user privileges | Role-based Security | |
| Best Use Case | For smaller, less complex applications. | Personal data, small businesses | Lightweight, Simplicity |
| For large, complex, and data-intensive applications. | Banking, enterprise apps | Enterprise, Scalability |
MCQ
Which of the following best defines DBMS?
A) A system that organizes data into related tables
B) A file-based system to manage and store data
C) A database management system with ACID compliance
D) A system specifically used for web applications
Answer: B
In RDBMS, data is stored in which structure?
A) Files
B) Trees
C) Tables
D) Objects
Answer: C
What is a primary key used for in RDBMS?
A) To enforce relationships between tables
B) To encrypt sensitive data
C) To store unstructured data
D) To create backup copies of a database
Answer: A
Which of the following is NOT a characteristic of DBMS?
A) No strict data relationships
B) Data stored in file formats
C) ACID compliance
D) Limited data integrity features
Answer: C
What type of query language is commonly used to interact with RDBMS?
A) XML
B) JSON
C) SQL
D) Assembly
Answer: C
Which of the following features is unique to RDBMS compared to DBMS?
A) Multi-user support
B) File-based data storage
C) Support for keys to enforce relationships
D) Basic security features
Answer: C
Which scenario is best suited for a DBMS?
A) Managing an e-commerce platform
B) Creating a personal budgeting app
C) Banking transactions involving multiple users
D) Storing data for a social media application
Answer: B
RDBMS is preferred over DBMS for applications requiring:
A) Simple data management
B) Complex relationships and large datasets
C) File-level security features
D) Offline data storage
Answer: B
Which term is related to ensuring reliable transactions in RDBMS?
A) Concurrency control
B) File locking
C) ACID compliance
D) Hierarchical structure
Answer: C
Which of these is NOT a feature of RDBMS?
A) Role-based security
B) Support for hierarchical data
C) SQL-based data accessibility
D) Relationship enforcement
Answer: B