SQL - Table ConstraintsWhy would a database designer choose to use a composite primary key instead of a single-column primary key?ATo uniquely identify records using a combination of multiple columnsBTo allow duplicate values in the primary key columnsCTo simplify queries by using only one column as the keyDTo avoid defining any unique constraints on the tableCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand primary keysA primary key uniquely identifies each record in a table.Step 2: Composite keysA composite primary key uses multiple columns together to ensure uniqueness.Final Answer:To uniquely identify records using a combination of multiple columns -> Option AQuick Check:Composite keys combine columns for uniqueness [OK]Quick Trick: Composite keys combine columns for uniqueness [OK]Common Mistakes:MISTAKESThinking composite keys allow duplicatesBelieving composite keys simplify queriesAssuming composite keys remove uniqueness
Master "Table Constraints" in SQL9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More SQL Quizzes Aggregate Functions - AVG function - Quiz 2easy LEFT and RIGHT JOIN - Why outer joins are needed - Quiz 5medium Set Operations - Set operation column matching rules - Quiz 14medium Set Operations - UNION ALL with duplicates - Quiz 6medium Subqueries - Nested subqueries - Quiz 7medium Subqueries - Subquery with IN operator - Quiz 5medium Subqueries - Subquery with IN operator - Quiz 14medium Subqueries - Subquery in WHERE clause - Quiz 2easy Table Constraints - NOT NULL constraint - Quiz 10hard Views - Querying through views - Quiz 8hard