What is RDBMS?
- Get link
- X
- Other Apps
- What is RDBMS?
- RDBMS stands for Relational Database Management System.
- All modern database management systems like SQL, MS SQL Server, IBM DB2, ORACLE, My-SQL, and Microsoft Access are based on RDBMS.
- A Relational Database is a database system that stores and retrieves data in a tabular format organized in the form of rows and columns.
- It is a smaller subset of DBMS which was designed by E.F Codd in the 1970s.
- Brief History of RDBMS:
- The history of Relational Database Management Systems (RDBMS) starts in the 1970s with E F. Codd’s work at IBM.
- Codd introduced the concept of relational databases in 1970 that use of SQL (Structured Query Language) for querying data.
- This model revolutionized data management by emphasizing data integrity and reducing redundancy.
- In the 1980s, commercial RDBMS products such as Oracle, IBM DB2, and Microsoft SQL Server emerged, making relational databases the industry standard for data management.
- Over the decades, RDBMS technology has continued to evolve, incorporating advancements in scalability, performance, and support for complex queries, cementing its role as a cornerstone of modern database management.
- Dr. E. F. Codd’s rules for RDBMS:
- Every database has tables, and constraints cannot be referred to as a rational database system.
- And if any database has only relational data model, it cannot be a Relational Database System (RDBMS).
- So, some rules define a database to be the correct RDBMS.
- These rules were developed by Dr. Edgar F. Codd (E.F. Codd) in 1985, who has vast research knowledge on the Relational Model of database Systems.
- Dr. Edgar F. Codd presents his 13 rules for a database to test the concept of DBMS against his relational model, and if a database follows the rule, it is called a true relational database (RDBMS).
- These 13 rules are popular in RDBMS, known as Codd's 12 rules.
- Rule 0: The Foundation Rule
- A relational database system must manage databases totally through its relational capabilities.
- Rule 1: Information Rule
- A database consists of information about user data or metadata.
- The information/data must be stored in the form of columns and rows in each and every cell of a table.
- Rule 2: Guaranteed Access Rule
- In a Relational database, every data value must be logically accessible by using a combination of the table name, primary key, column name, etc.
- Rule 3: Systematic Treatment of Null Values
- The Treatment of null values should be a systematic way.
- The null values in RDBMS are used for only missing information, empty values, or not applicable values.
- Rule 4: Active/Dynamic Online Catalog based on the relational model
- The entry structure of the database must be stored in an online catalog which is known as Data Dictionary.
- So, the authorized user can access data through the query language.
- Rule 5: Comprehensive Data Sublanguage Rule
- An RDBMS support several languages to access the database.
- We should use language that must be well having linear syntax and supports various operations such as data definition, view definition, data manipulation, integrity constraints, authorization, and transaction management operations (begin, rollback, and commit).
- Rule 6: View Updating Rule
- The relational database system has different types of views and these all views can theoretically and practically be updatable by the database system.
- Rule 7: Relational Level Operation (High-Level Insert, Update and delete) Rule
- A relation database system must support relational operations rules such as high-level insertion, update, and deletion of data at each level of relation. It also supports the union, intersection, and minus operations.
- Rule 8: Physical Data Independence Rule
- To access data in the Database it should independent physically. Each data in the database should depend on other data.
- Any change in the location of the file does not effect on structure of the table.
- Rule 9: Logical Data Independence Rule
- Any change in the conceptual schema does not affect the external schema.
- Making changes in the structure of the database(table) does not affect the database file.
- Data in the database must be independent of its user's views.
- Rule 10: Integrity Independence Rule
- A database should be independent of the application that manages entire databases and the integrity of data should not affect the application level or external level.
- It also makes a database independent of the front-end application and its interface.
- Rule 11: Distribution Independence Rule
- The end user must not able to see a distribution of data over several locations.
- Users should always get the impression that the data is located at one site only. if any user is accessing the database, the user doesn't know that another user is also accessing the same database and the data they get are available at the same place only.
- Thus, the data must be independent of each user to access it.
- Rule 12: Non-Subversion Rule
- If RDBMS has a low-level language other than SQL then it should not subvert or bypass the integrity rule.
Difference between DBMS vs. RDBMS
Features DBMS RDBMS Full Form Database Management System Relational Database Management System Data Storage Data
is stored as files. Data
is stored in tables. Data Relationships Does not enforce relationships between data. Enforces relationships between tables using keys. Data Integrity No
integrity constraints. Enforces
integrity constraints like primary key, foreign key. Normalization Not necessarily used. Frequently used to eliminate redundancy. Query Language Uses
various query languages depending on the system. Uses
Structured Query Language (SQL). Data Redundancy More prone to data redundancy. Reduces data redundancy through normalization. Support for ACID Properties May
not fully support ACID properties. Fully
supports ACID properties (Atomicity, Consistency, Isolation, Durability). Security Basic security features. Enhanced security features including user permissions. Examples File
systems, XML databases. MySQL,
PostgreSQL, Oracle, Microsoft SQL Server. Scalability Limited scalability. Highly scalable. Data Manipulation Less
efficient for complex queries. Efficient
for complex queries using SQL. Transactions May not support transactions. Supports transactions with ACID properties. User Interface Generally
lacks a graphical user interface. Often
comes with a graphical user interface for ease of use. Usage Suitable for small-scale applications. Suitable for large-scale applications requiring complex data
relationships.

Comments
Post a Comment