Practical Issues of Data Placement

Slides:



Advertisements
Similar presentations
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide
Advertisements

Chapter 18 Methodology – Monitoring and Tuning the Operational System Transparencies © Pearson Education Limited 1995, 2005.
Topic Denormalisation S McKeever Advanced Databases 1.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Key.
Chapter Physical Database Design Methodology Software & Hardware Mapping Logical Design to DBMS Physical Implementation Security Implementation Monitoring.
IS 4420 Database Fundamentals Chapter 6: Physical Database Design and Performance Leon Chen.
Physical Database Monitoring and Tuning the Operational System.
Modern Systems Analysis and Design Third Edition
PARTITIONING “ A de-normalization practice in which relations are split instead of merger ”
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
Chapter 6 Physical Database Design. Introduction The purpose of physical database design is to translate the logical description of data into the technical.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 9.1.
Practical Database Design and Tuning. Outline  Practical Database Design and Tuning Physical Database Design in Relational Databases An Overview of Database.
CSC271 Database Systems Lecture # 30.
1 © Prentice Hall, 2002 Physical Database Design Dr. Bijoy Bordoloi.
TM 7-1 Copyright © 1999 Addison Wesley Longman, Inc. Physical Database Design.
Physical Database Design Chapter 6. Physical Design and implementation 1.Translate global logical data model for target DBMS  1.1Design base relations.
Lecture 12 Designing Databases 12.1 COSC4406: Software Engineering.
CORE 2: Information systems and Databases NORMALISING DATABASES.
Chapter 6 1 © Prentice Hall, 2002 The Physical Design Stage of SDLC (figures 2.4, 2.5 revisited) Project Identification and Selection Project Initiation.
© Pearson Education Limited, Chapter 15 Physical Database Design – Step 7 (Consider Introduction of Controlled Redundancy) Transparencies.
Chapter 16 Practical Database Design and Tuning Copyright © 2004 Pearson Education, Inc.
IMS 4212: Database Implementation 1 Dr. Lawrence West, Management Dept., University of Central Florida Physical Database Implementation—Topics.
CIS 210 Systems Analysis and Development Week 6 Part II Designing Databases,
Database Management COP4540, SCS, FIU Physical Database Design (ch. 16 & ch. 3)
Physical Database Design Purpose- translate the logical description of data into the technical specifications for storing and retrieving data Goal - create.
CHAPTER 2 : RELATIONAL DATA MODEL Prepared by : nbs.
1 Information Retrieval and Use De-normalisation and Distributed database systems Geoff Leese September 2008, revised October 2009.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 12 Designing.
IT 5433 LM4 Physical Design. Learning Objectives: Describe the physical database design process Explain how attributes transpose from the logical to physical.
Converting ER/EER to logical schema; physical design issues 1.
Practical Database Design and Tuning
Understanding Data Storage
Databases Chapter 9 Asfia Rahman.
Record Storage, File Organization, and Indexes
SEEM3430: Information Systems Analysis and Design
Physical Changes That Don’t Change the Logical Design
Conceptual and Physical Database Design
Database Management System
Physical Database Design and Performance
CIS 155 Table Relationship
ITD1312 Database Principles Chapter 5: Physical Database Design
Methodology – Monitoring and Tuning the Operational System
Physical Database Design for Relational Databases Step 3 – Step 8
Modern Systems Analysis and Design Third Edition
Chapter 4 Relational Databases
Databases A brief introduction….
Translation of ER-diagram into Relational Schema
CHAPTER 5: PHYSICAL DATABASE DESIGN AND PERFORMANCE
Chapter 9 Designing Databases
Chapter 3 The Relational Database Model
Order Database – ER Diagram
Normalization Referential Integrity
Session #, Speaker Name Indexing Chapter 8 11/19/2018.
Chapter 9 Designing Databases
Chapter 6 Normalization of Database Tables
Physical Database Design
Chapter 12 Designing Databases
Chapter 6: Physical Database Design and Performance
Practical Database Design and Tuning
Relational Database Model
Chapter 10 Designing Databases
The Physical Design Stage of SDLC (figures 2.4, 2.5 revisited)
Methodology – Monitoring and Tuning the Operational System
System Analysis and Design
Chapter 17 Designing Databases
CSE594: REVIEW.
Systems Analysis and Design, 7e Kendall & Kendall
DBMS Physical Design Physical design is concerned with the placement of data and selection of access methods for efficiency and ongoing maintenance.
Database Design Chapter 7.
Presentation transcript:

Practical Issues of Data Placement Physical Design Practical Issues of Data Placement

Access efficiency Driven by number of disk reads Join logic SELECT * FROM A, B WHERE A.KEY = B.KEY AND A.CONDITION = TRUE; Read Key A IF condition = TRUE Read All B’s Match current A Read Next A

Improving Efficiency Indexing Denormalization Partitioning Locate specific records quickly Denormalization Reduce the number of joins Partitioning Reduce the amount of data

INDEXES: PRIMARY KEY INDEXES Maintain record integrity by assuring that no duplicate values exist CREATE UNIQUE INDEX PRODINDEX ON PRODUCT (PRODUCT_NO);

Indexes: Nonkey Indexes Allow efficient access to files using non-key data. CREATE INDEX DESCRIP ON PRODUCT (DESCRIPTION);

Indexes: Clustering Indexes Determine the physical storage sequence for data CREATE INDEX DESCRIP ON PRODUCT (DESCRIPTION) CLUSTER;

Denormalization Selective violations of normalization principles for access efficiency Entities with 1:1 relationships. It may be wise to combine these into a single table.

Denormalization M:N relationships with non-key attributes (gerunds). Extracting attributes from one entity into another requires a join that accesses the link file and the associated entity. It may be worth violating 2NF or 3NF rules to duplicate commonly needed attribute values in the link file or even in the "parent" entity.

Denormalization Reference data. These are 1:M relationships in which the 1 side is a lookup table for indicator keys in the "many" file. If these lookups are not used in many files and there are not many instances of the "many" entity for each "one" occurrence, it may be a good idea to move the reference attributes to the parent file and violate 3NF.

Partitioning Splitting data into groups for improved performance Vertical Select frequently used attributes for a primary table and transfer others to a sub-class file that is less frequently accessed Horizontal Duplication

Distributed Data (Maintaining Concurrency) Two Phased Commit Prepare commit by locking all versions Execute the commit simultaneously