Category: Database Management Systems (DBMS)

Tags: DBMS, Database, SQL, MySQL, Oracle Database, NoSQL, Cloud Computing

Introduction

In the modern digital world data is absolutely critical to virtually every organisation. Banks have customer transaction data, universities have student data, hospitals have patient data and ecommerce sites have product data and order data. Getting that data managed effectively is a major requirement.

A database is an organised collection of related data which can be stored, retrieved and updated as and when required. A Database Management System (DBMS) is the software which allows you to create, manage, retrieve and protect the data.

Popular DBMS's are MySQL, Oracle Database, Microsoft SQL Server, PostgreSQL and MongoDB. These technologies are used to support applications from small sites right up to the largest of enterprise applications.

In this article we look at the history of database applications, when a DBMS is required, its principal advantages and some of the real world applications.

Brief History of Database Applications

Database technology has evolved enormously over the past few decades with each stage bringing new techniques for organising information and dealing with the problems of data management.

1.1 Traditional File-Based Systems

Prior to the advent of modern databases, organisations managed their information in the form of paper records, registers and individual computer files. For instance a college might have onefile with the student data, one file with the examination results and one file with the fee information.

file with the student data, one file with the examination results and one file with the fee information.

These constraints led to the requirement for more systematic data management solutions.

1.2 Hierarchical Database Model

The hierarchical database model organised data in a tree structure with parent and child records. For instance a company could have a number of departments, each of which would in turn have a number of employees. IBM's Information Management System (IMS) of the late 1960s was a key example of hierarchical database technology. Hierarchical databases offered very efficient access to the pre-defined relationships but were less flexible when you needed to have complex relationships between records in an application.

1.3 Network Database Model

The network database model was an improvement on the hierarchical model in that a record could have multiple relationships. For example one student could be enrolled in several courses and each course could have many students. The network model did allow for more complex relationships, but the data structures and the way you navigated them could be very difficult to maintain.

1.4 Relational Database Model

In 1970 Codd, the computer scientist, published his paper 'A Relational Model of Data for Large Shared Data Banks' in which he introduced the relational model. The relational model is all about organising data in tables (rows and columns) and then linking those tables together via keys. That makes it very easy to represent the relationships that exist between different types of information.

Consider a simple student database:

A separate table can store the examination results and use the Student_ID to link each result to the relevant student.

SQL (Structured Query Language) enables you to retrieve and manipulate data stored in a relational database. The popular relational DBMS products are MySQL, Oracle Database, PostgreSQL and Microsoft SQL Server. Relational databases became so popular because they offer structured data management, integrity constraints, flexible querying and reliable transactions.

1.5 Object-Oriented and Object-Relational Databases

As software applications got more complex the need arose for ways to manage data of all kinds (multimedia, engineering designs, complex objects etc). Object oriented databases store the data as objects. Object relational databases combine the capabilities of a relational database with support for additional data types and structures. These technologies found uses in scientific research, engineering, multimedia and in a number of specialist enterprise systems.

1.6 Data Warehousing and Business Intelligence

In the 90s and into the early 2000s organisations increasingly used historical data to understand their business and make decisions. Data warehouses pulled together data from a number of sources in order to support reporting and analysis. For instance a retailer could look at sales data from their various branches to work out which products are their bestsellers and what the seasonal demand is Data warehousing and BI became crucial for financial analysis, forecasting, CRM and strategic planning.

1.7 NoSQL and Distributed Databases

As the internet grew, with social media and all sorts of large web applications, organisations started to be dealing with huge amounts of both structured and unstructured data.NoSQL databases became popular for workloads that are well served by a flexible data model, a distributed architecture or some specific scaling approach.

Common types include:

For instance a web app might be using MongoDB to store its document based records, and a recommendation engine might be using a graph database to represent the relationships.

NoSQL databases don't necessarily replace relational databases in all situations. The right choice will be dependent on the application's data model, its consistency requirements, its workload and its scalability requirements.

1.8 Cloud Databases and Modern Applications

Cloud computing has changed the way we deploy and maintain databases. Rather than having to manage the database servers themselves, organisations can now use managed database services.

Examples are Amazon RDS, Amazon Aurora, Azure SQL Database and Google Cloud SQL.

Modern databases support cloud apps, mobile platforms, real time systems, analytics and AI.

Vector databases have also come under the spotlight in relation to similarity search and AI powered applications.

Databases are absolutely fundamental to web development, cloud computing, DevOps and enterprise software today.

When should we use a DBMS?

A DBMS is useful when you've got an application that needs to store, retrieve, update, share and protect data in a reliable way.

2.1 When managing large amounts of data

When you're dealing with tens of thousands or indeed millions of records, plain old files can become a bit of a nightmare to manage.

A DBMS helps to organise the information and allows you to retrieve specific records very efficiently.

Example: A university uses a DBMS to manage student records (profiles), attendance, results and fees.

2.2 When multiple users need access

A DBMS is useful when you have multiple users or applications all wanting to access and update the same data. It provides concurrency control to prevent conflicting operations.

Example: A number of bank branches may require access to customer account information as the transaction is being processed.

2.3 When data accuracy is important

A DBMS uses rules like primary keys, foreign keys, unique constraints, and data validation.

These features help to prevent bad records and keep the data integrity.

Example: An examination result should reference an actual student rather than an invalid student ID.

2.4 When security is required

Database systems provide authentication, authorisation and access permissions.

Admins can restrict users to the information and operations that they need to do their job.

Example: Within a hospital environment doctors and billing staff may have different levels of access to patient information.

2.5 When reliable transactions are required

Transactions are absolutely vital when you need a number of operations to all succeed together.

Relational databases commonly support ACID properties:

Atomicity: a transaction either completes or it doesn't. Consistency means a transaction keeps the database rules in place.

Isolation: Concurrent transactions are isolated to prevent improper interference.

Durability: committed changes are preserved in accordance with the database's durability guarantees.

Example: In a bank transfer the funds are drawn from one account and credited to another as part of a legitimate transaction.

2.6 When Backup and Recovery are important

Organisations need to protect data against accidental deletion, hardware failure and software error. Database systems can provide backups, transaction logs, replication and recovery.

Example: An e-commerce site needs to be able to recover order data following a server failure.

These mechanisms have to be configured and tested appropriately to ensure that recovery actually works when it's required.

Why should we use a DBMS?

A DBMS offers many benefits compared to old file-based ways of managing data.

3.1 Reduced Data Redundancy

Data redundancy is where the same data is stored in multiple places. A well designed database eliminates duplication by putting the data into related tables or collections.

3.2 Improved Data Consistency

When you have the same information in multiple files it can be a real pain to update all of the copies. A DBMS maintains consistency via centralised data management, constraints and transactions.

3.3 Better Data Security

A DBMS enables the administrator to control who can read, insert, update or delete information. This is absolutely critical in the banking, healthcare, education and business sectors.

3.4 Easy Data Retrieval

SQL enables the user to get at the information they require via queries.

For example:

SELECT * FROM Students WHERE Course = 'MCA';

This query returns the records for the MCA students (assuming of course the table and column names are as per the database schema).

3.5 Data Integrity

Data integrity means ensuring the accuracy and validity of the data that is stored.

Primary keys, foreign keys, unique constraints and all the other validation rules are there to ensure that the data in the database is in the right format.

3.6 Data Independence

Data independence means that changes can be made to the way data is stored or organized in a database without having to change every application that uses it. This is important because it allows the database to grow and improve over time. Applications stay functional when the underlying structure changes. It makes the system easier to maintain and update.

3.7 Concurrent Access

A database management system lets many users access the database at the same time. It manages these accesses carefully to avoid conflicts. For instance in a shopping site if only one item is left the system must make sure two people don’t both buy it. The DBMS controls access so that one user sees the item as available while the other gets a message that it’s gone. This prevents errors. Keeps data accurate.

3.8 Backup and Recovery

Backup and recovery are key parts of keeping data safe. Backups create copies of data and recovery lets organizations restore that data if something goes wrong like a system crash or accidental deletion. These features are essential for protecting information. Regular backups must be tested to make sure they work when needed. Without them data loss could cause problems.

3.9 Easier Application Development

Using a database management system helps developers build applications faster. It offers tools to store, find, update and manage data. Developers don’t need to write everything from the beginning. They can use the DBMS to handle data operations. This frees up time to focus on what the application should do not how to manage data.

3.10 Better Decision-Making

Databases help businesses make decisions. They support reports, dashboards and analysis. Companies can look at sales trends, customer behavior and performance metrics. This makes it easier to plan and improve services. With timely data decisions are more informed and effective. Data-driven insights help organizations stay competitive.

Real-World Applications of DBMS

Database management systems are used in industries to manage data and support daily operations.

These examples show how databases help organizations handle information efficiently and run smoothly.

When Is a DBMS Not Necessary?

A database management system is very useful.. It is not needed for every application. Simple tasks like a to-do list, a static website or a small script may work fine with a text file, CSV file or JSON file.

A full DBMS might be unnecessary when:

When an application grows and needs concurrent access, reliable transactions, complex data searches or centralized data control a DBMS becomes a better option.

Database technology has come a way. It started with file systems and moved through hierarchical and network models to relational, NoSQL and cloud-based systems. Each step improved how data was organized accessed, scaled and protected. Today a database management system is crucial when applications need fast data access, data integrity, security, concurrent use, transaction control and backup and recovery.

From banking and healthcare to online shopping and cloud platforms databases power digital services. Choosing the database depends on the application’s needs, the kind of data the expected load, the budget and reliability goals. A chosen and properly built database helps organizations manage data well and create secure, reliable and scalable applications.

References

IBM. Information Management System (IMS)

https://www.ibm.com/history/information-management-system

IBM Research. A Relational Model of Data, for Large Shared Data Banks

https://research.ibm.com/publications/a-relational-model-of-data-for-large-shared-data-banks

IBM. History of the Relational Database

https://www.ibm.com/history/relational-database

Oracle. Database Concepts

https://docs.oracle.com/en/database/oracle/oracle-database/26/cncpt/

MongoDB. Documentation

https://www.mongodb.com/docs/manual/

MongoDB. Document Databases

https://www.mongodb.com/resources/basics/databases/document-databases