Why Government Websites Ask So Many Questions: Understanding RDBMS Through Everyday Government Services

A Simple Guide for Citizens, Government Employees, Students and Professionals

By Chinzakhual Khuptong (Steve), MCA

Introduction

Whether we realize it or not, most of us interact with a government database almost every day.

We update our Aadhaar details, check voter information, apply for scholarships, register for government jobs, receive pensions, use digital health services, pay taxes, link bank accounts, or download certificates. To us, these activities appear simple—we fill in an online form, click Submit, and within a few seconds the website responds.

Sometimes it displays “Application Submitted Successfully.”

Sometimes it says “Record Already Exists.”

Sometimes it reports “Details Do Not Match.”

Many people assume that these websites simply store information. In reality, they perform many complex tasks behind the scenes—validating data, searching millions of records, checking relationships between information, preventing duplicate entries, retrieving previous records, and displaying only the information the user is authorized to see.

Behind most of these systems is a technology called the Relational Database Management System (RDBMS).

In an earlier article, I explained what a Database Management System (DBMS) is. In this article, we take the next step by understanding what makes an RDBMS different and why it has become the backbone of modern digital government.

Imagine a Government Office Before Computers

Before computers became common, government offices depended almost entirely on paper files.

Imagine entering a district office thirty years ago. Steel cupboards filled every room. Thousands of paper files were arranged on shelves. If an officer wanted to locate one citizen’s record, someone had to search through folders manually. Updating one address might require changing several files in different departments. Duplicate records and missing files were common.

Computers changed this process completely.

Instead of storing information in paper files, they store it in carefully organized electronic structures called tables.

What Is a Table?

The word table sounds technical, but the idea is simple.

If you have ever used Microsoft Excel or even written information in a notebook with rows and columns, you have already used something very similar.

A database table is simply an organized collection of similar information.

Citizen ID	Name	Date of Birth	District
1001	Rahul Kumar	12-05-1998	Delhi
1002	Sita Devi	03-09-1996	Jaipur
1003	Amit Singh	25-11-2000	Bhopal

Each row represents one citizen. Database professionals call each row a record.

Each column stores one type of information, called a field.

Instead of maintaining thousands of paper files, the computer stores millions of such records electronically.

How You Experience This as a Citizen
When you submit an online application, the system usually creates a new record inside the appropriate table. Your application becomes one row among millions of other rows.

Why Every Table Needs a Primary Key

Now imagine that there are hundreds of citizens named Rahul Kumar.

If a government officer searches only by name, which Rahul Kumar should the computer choose?

The computer therefore needs one value that identifies exactly one record.

This unique identifier is called the Primary Key.

Think of it as the house number of a building. Many people may live on the same street, but every house has a unique number.

Similarly, every record in a table must have one unique identity.

The important rule is simple:

No two records can have the same Primary Key.

How You Experience This as a Citizen
When you enter an application number to check your status, the system uses that unique identifier to locate your exact record.

Why Does the Database Need More Than One Table?

Suppose one citizen has:

a bank account,
a scholarship application,
a pension record,
a land record,
a driving licence,
and several tax payments.

Should all of this information be stored in one giant table?

No.

Different types of information belong in different tables because each serves a different purpose. This makes the system easier to maintain, faster to search, and less prone to errors.

What Is a Foreign Key?

If citizen information is stored in one table and bank accounts in another, how does the computer know which bank account belongs to which citizen?

The answer is the Foreign Key.

A foreign key is simply a value that refers to a related record in another table.

Think of it as writing a file number on another document instead of photocopying the entire file.

Instead of copying the citizen’s complete details into every table, the system stores a reference.

This reference creates a logical relationship between different tables.

How You Experience This as a Citizen
When a government portal displays your profile together with your application history or payment status, it is often retrieving related information from several tables using these relationships.

What Does “Relational” Mean?

The word Relational simply means that different tables are logically connected.

Think about a family.

A father, mother, and children each have their own identities, yet they are related.

Likewise, a citizen table, a payment table, and an application table remain separate but are connected through carefully defined relationships.

This organization keeps information accurate and avoids unnecessary duplication.

Important: Different government departments usually maintain separate databases and their own internal identifiers. Where information is shared, it typically happens through authorized verification services or approved data exchanges—not through one giant national database.

What Is Normalization?

Imagine writing your home address in ten different notebooks.

When you move to another city, you must update all ten copies.

If one copy is forgotten, conflicting information appears.

Normalization is the process of organizing data to reduce unnecessary duplication.

Instead of storing the same information repeatedly, a well-designed database stores it once where appropriate and allows related tables to refer to it.

Normalization offers several advantages:

Less duplicate information
Smaller storage requirements
Easier updates
Fewer mistakes
Better consistency

How You Experience This as a Citizen
If one department updates your address, another department may still show the old address because each maintains its own database. Information sharing between departments follows authorized processes and is not always automatic.

What Happens After You Click “Submit”?

Many people believe that clicking Submit simply saves the form.

In reality, the system may:

Check mandatory fields.
Validate dates and identification numbers.
Look for duplicate records.
Verify related information where required.
Store the new record.
Retrieve updated information.
Display a confirmation message.

All of this usually happens within a few seconds.

Why Are Government Websites So Fast?

Searching millions of records one by one would be far too slow.

Instead, databases use indexes, which work much like the index of a book. Rather than reading every page, the database follows organized lookup structures that point directly to the required information.

Why Can Different Officers See Different Information?

Not every government employee should have access to every detail.

Databases use views, permissions, and role-based access control so that each officer sees only the information needed for their work.

This improves both privacy and security.

Conclusion

The true strength of an RDBMS is not simply storing information. Its real power lies in organizing data, maintaining logical relationships, preventing duplication, validating entries, retrieving records quickly, and supporting secure access for millions of users.

Every online application, certificate download, pension payment, scholarship approval, or status enquiry depends on these principles.

Once we understand concepts such as tables, records, primary keys, foreign keys, relationships, normalization, and indexes, government websites become much easier to understand.

Technology is not magic. It is organized logic working quietly behind every digital service we use.

About the Author

Chinzakhual Khuptong (Steve), MCA

The author writes about information technology, digital governance, artificial intelligence, cloud computing, and cybersecurity in simple language. His aim is to bridge the gap between complex technology and everyday understanding so that students, government employees, professionals, and ordinary citizens can confidently understand the digital systems they use every day.

Anything for a BETTER WORLD!!!