DBMS – Data Base Management System
RDBMS – Relational Data Base Management System or Relational DBMS
A DBMS has to be persistent, that is it should be accessible when the program created the data ceases to exist or even the application that created the data restarted. A DBMS also has to provide some uniform methods independent of a specific application for accessing the information that is stored.
RDBMS adds the additional condition that the system supports a tabular structure for the data, with enforced relationships between the tables. This excludes the databases that don’t support a tabular structure or don’t enforce relationships between tables. The father of RDBMS is famous Mathematician E. F. Codd.
DBMS does not impose any constraints or security with regard to data manipulation it is user or the programmer responsibility to ensure the ACID Properties of the database whereas the RDBMS is more with this regards because RDBMS defines the integrity constraint for the purpose of holding ACID Properties. RDBMS may be or may not be Client Server Database System.
See the Comparison Chart:
|Concept||No relationship concept||Establishes Relationships concepts with two DB Objects (e.g. tables, views etc)|
|Data Treatment||Data as files internally||Data as Tables Internally|
|Accessibility||Support Single User||Support Multiple Users|
|Rules||Support 3 Rules of “Codd’s 12 Rules of relational Model”||Support minimum 6 Rules of “Codd’s 12 Rules of relational Model”|
|Infrastructure||Low Software and Hardware Requirements||High Software and harware requirements|
|Examples||XML, FoxPro||SQL Server, Oracle|