TAILIEUCHUNG - Lecture Database system concepts (5/e): Chapter 7 - Silberschatz, Korth, Sudarshan 

This chapter introduces the theory of relational database design. The theory of functional dependencies and normalization is covered, with emphasis on the motivation and intuitive understanding of each normal form. This chapter begins with an overview of relational design and relies on an intuitive understanding of logical implication of functional dependencies. | Chapter 7: Relational Database Design Chapter 7: Relational Database Design Features of Good Relational Design Atomic Domains and First Normal Form Decomposition Using Functional Dependencies Functional Dependency Theory Algorithms for Functional Dependencies Decomposition Using Multivalued Dependencies More Normal Form Database-Design Process Modeling Temporal Data The Banking Schema branch = (branch_name, branch_city, assets) customer = (customer_id, customer_name, customer_street, customer_city) loan = (loan_number, amount) account = (account_number, balance) employee = (employee_id. employee_name, telephone_number, start_date) dependent_name = (employee_id, dname) account_branch = (account_number, branch_name) loan_branch = (loan_number, branch_name) borrower = (customer_id, loan_number) depositor = (customer_id, account_number) cust_banker = (customer_id, employee_id, type) works_for = (worker_employee_id, manager_employee_id) payment = (loan_number, payment_number, payment_date, payment_amount) savings_account = (account_number, interest_rate) checking_account = (account_number, overdraft_amount) Combine Schemas? Suppose we combine borrower and loan to get bor_loan = (customer_id, loan_number, amount ) Result is possible repetition of information (L-100 in example below) A Combined Schema Without Repetition Consider combining loan_branch and loan loan_amt_br = (loan_number, amount, branch_name) No repetition (as suggested by example below) What About Smaller Schemas? Suppose we had started with bor_loan. How would we know to split up (decompose) it into borrower and loan? Write a rule “if there were a schema (loan_number, amount), then loan_number would be a candidate key” Denote as a functional dependency: loan_number amount In bor_loan, because loan_number is not a candidate key, the amount of a loan may have to be repeated. This indicates the need to decompose bor_loan. Not all decompositions are good. Suppose we decompose employee into employee1 = .

• Cơ sở dữ liệu
• Database system
• Lecture Database system
• Relational databases
• Database design
• Relational database design
• Database design process
• Database system concepts
• Lecture Database system concepts
• Database systems
• Database languages
• Database system architectures
• Database system architecture
• File based approach
• Data management systems framework
• Recovery system
• Lecture Database systems
• Database architecture
• Database approach
• Query optimization
• Transaction state
• Concurrency control
• Data analysis
• Information retrieval
• Parallel databases
• Distributed databases
• Advanced application development
• Advanced data types
• Advanced transaction processing
• Relational model
• Basic query structure
• Dynamic SQL
• Tuple relational calculus
• Entity relationship model
• Application design
• Object­ based databases