MGS 351 Study Guide - Midterm Guide: Database Normalization, Database Design, Referential Integrity

• School: University at Buffalo
• Department: Management Science and Systems
• Course: MGS 351
• Professor: David Murray

Document Summary

Mgs351 review sheet exam 2: relational database design. Entity relationship diagrams diagramming tool used to design a relational database (blueprint) If designed properly, an erd will accurately reflect the business rules of the organization. It will become a visual illustration of the organization"s business rules: corrections are harder than adding on, 1:1, 1:n, n:m, entities = rectangles, lines = relationships, crows feet three lines connecting in a many. Identify all exceptions to the rule often difficult to define even if you are the business expert. Transforming erd"s to tables: entities tables, attributes fields, key attributes primary key, ensure all relationships simplify to a 1:n (1) 1:1 relationships merge into one table. Primary key of intersection table- combine (composite) primary keys or autonumber. ** turn any m:m or 1:1 into a 1:m relationships ** Data hierarchy: database, table (file, relation, records (rows, fields (columns, attributes, bytes, bits. Know data hierarchy from test 1 and know the synomous terms above.