Q.Compared to a file system, how does a database management system avoid redundancy in data through a database?

Data Redundancy Elimination

Think about your wardrobe. You own one black blazer that works for every formal occasion — but somehow you end up with three nearly identical black blazers, each taking up space, each needing to be cleaned and maintained. That extra space in your cupboard is wasted. That extra effort in upkeep is wasted. Now imagine that same problem, but with data stored across a large organisation.

Data redundancy elimination is the process of identifying and removing duplicate copies of the same piece of information from a database or storage system. It is not about deleting data you need — it is about ensuring that the same fact, figure, or record is stored exactly once, and every other place that needs it simply points back to that single original.

Why does redundancy happen in the first place?

In any real-world organisation, data enters through many doors. A customer's address might be recorded by the sales team when they place an order, by the support team when they register a complaint, and by the marketing team when they run a campaign. Each team works in its own system, often unaware that the same address already exists elsewhere. Over time, the same customer name, the same product code, or the same transaction record gets stored in multiple places — sometimes with slight differences, sometimes as exact copies.

This is not a technical glitch. It is a natural consequence of how organisations grow and how different departments work independently.

What makes redundancy a problem?

Redundancy is not harmless. It creates three serious issues:

• Wasted storage space — every duplicate copy consumes disk space, memory, and backup capacity. For a small business this may be trivial, but for a bank, a government department, or an e-commerce platform, the cost of storing millions of duplicate records adds up fast.

• Data inconsistency — this is the more dangerous problem. If a customer's address is stored in five places and they move house, updating all five copies is tedious and error-prone. One copy gets updated, another is forgotten. Now the same customer has two different addresses in the same system. Which one is correct? The system cannot tell you. The data has lost its integrity.

• Slower performance — searching through a bloated database, running reports, or generating invoices takes longer when the system has to wade through duplicate records. Every query becomes heavier than it needs to be.

How is it done in practice?

The process works at two levels.

At the database design level, redundancy is prevented before it happens. This is done through a technique called normalisation — breaking a large table into smaller, related tables so that each piece of information lives in exactly one place. For example, instead of storing a customer's name and address alongside every order they place, you store the customer details once in a separate table and link each order to that single record using a customer ID.

At the storage system level, redundancy is removed after the fact. Special software scans the stored data, identifies identical blocks or files, and replaces duplicates with pointers to a single copy. This is common in backup systems and cloud storage, where the same file might be saved by hundreds of users.

A concrete example …