What is the primary purpose of normalization in database design?

Normalization is a systematic approach to organizing a database in order to minimize redundancy and dependency. The primary goal is to eliminate data anomalies that can occur during data insertion, deletion, or update operations. By dividing large tables into smaller ones and defining relationships between them, normalization reduces redundancy and ensures that each piece of data is stored only once. This process involves several normal forms (1NF, 2NF, 3NF, etc.) each with specific criteria for organizing data effectively. Option A (To increase redundancy) is incorrect because normalization seeks to reduce redundancy, not increase it. Option B (To improve performance by reducing join operations) is misleading; while it can lead to more efficient data handling, the main focus of normalization is on data integrity and reducing redundancy. Option D (To create complex relationships between tables) is inaccurate; normalization aims for simplicity in relationships rather than complexity. Option E (To enforce security constraints) is not a primary goal of normalization; security constraints are typically enforced through access controls and other means.