Fundamentals of Database Management Systems Referential integrity “rules” trigge
ID: 667124 • Letter: F
Question
Fundamentals of Database Management Systems
Referential integrity “rules” trigger some cleanup of your data when insertion, update, or deletion events would typically cause data anomalies. But the word “trigger” has its own place in database design and implementation. Research the concept of a “trigger” and compare and contrast “trigger” events with referential integrity rules. And discuss the concept of the intersection table. Why is it needed in many to many relationships? Why is intersection data needed?
Explanation / Answer
An intersection table implements a many-to-many relationship between two business components. A many-to-many relationship is one in which there is a one-to-many relationship from either direction
To implement a many-to-many relationship, two links and a table designated as an intersection table are required. The table is designated as an intersection table in its Type property by means of a value of Data (Intersection). The intersection table represents the many-to-many relationship as two one-to-many relationships, which the underlying DBMS is designed to handle. There is no database construct that implements many-to-many relationships directly
An intersection table is a table that defines a many-to-many relationship. It provides an intersection between two business components. A many-to-many relationship is one in which there is a one-to-many relationship from either direction. For example, there is a many-to-many relationship between Accounts and Contacts
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.