Normalization & Schema Design · SQL SQL
When is intentional denormalization typically justified in a production relational database?
Practice question from Normalization & Schema Design (SQL SQL), with the correct answer and a step-by-step solution.
medium · MCQ · Q-5D0D36
When is intentional denormalization typically justified in a production relational database?
- A.To prevent all write update anomalies during frequent insert operations.
- B.To improve read performance and reduce expensive joins on high-traffic queries.Correct answer
- C.To comply with mandatory ANSI SQL standards for cloud databases.
- D.To ensure that every table contains duplicate primary key values.
Solution
Denormalization introduces redundancy back into the schema intentionally to trade off write performance and storage space for faster read performance by eliminating expensive multi-table joins.
More from Normalization & Schema Design
- What is the primary objective of normalizing a database to the Third Normal Form (3NF)?
- A relation R(A, B, C, D) has the functional dependencies F = {AB -> C, C -> D, D -> A}. What is the highest normal form satisfied by R?
- Which of the following describes a Boyce-Codd Normal Form (BCNF) violation?
- What type of data anomaly occurs when deleting a record inadvertently causes other unrelated domain information to be lost from the databas…
Practise more SQL
Sign up free for adaptive practice on this chapter, with instant feedback and hints on every question.
Start practising freeFree to start · No credit card needed