Problems in Traditional file oriented approach

The traditional file-oriented approach involves each application managing its own data in independent files. While simple and cost-effective for basic tasks, it suffers from several major structural and operational problems:

• Redundancy: The same piece of information is often duplicated in multiple files across different departments.
• Inconsistency: When redundant data is updated in one file but not in others, it leads to mismatched information.

• Program-Data Dependency: If the file format changes (e.g., adding a new field), every program that accesses that file must be rewritten.
• Data Isolation: Data is scattered in various files with different formats, making it difficult to write new programs to retrieve and integrate related information.

• Limited Data Sharing: Because files are private to specific applications, sharing data across different departments is restricted.
• Lack of Atomicity: File systems do not natively support “all-or-nothing” transactions. 

• Weak Security: It is difficult to enforce fine-grained access rights. 
• Integrity Problems: There is no centralized way to enforce “business rules” (constraints).