Cartesian Data
From the book I Am Datapedia!, published here free by the author.
Part of I Am Datapedia!
Questions 1–10 of 10
1. What is Cartesian Data about?
2. What should a data modeller introduce when two tables have a 'Many to Many' relationship?
3. Why does joining the Sales table directly to the Target table on Employee ID produce Cartesian data?
4. Which department is said to get nightmares from Cartesian data, seeing USD 200k when they know the total is USD 100k?
5. Even with an intermediary table in place, what can still cause Cartesian data?
6. In the John example, how many rows are produced when Employee, Target and Sales are joined in one query?
7. What is the correct row count after resolving the John example with UNION ALL?
8. In the department and salary example, how many rows result from joining Dept (2 rows for an employee) and Sal (12 monthly rows) on Employee ID?
9. How should the Dept and Sal tables be joined to avoid Cartesian data?
10. Which of the following is NOT listed as a cause or symptom of Cartesian data?