Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

12
Copyright, Harris Corporation & Ophir Frieder, 1998 1 Database Design

Transcript of Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Page 1: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Copyright, Harris Corporation & Ophir Frieder, 1998

1

Database Design

Page 2: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Copyright, Harris Corporation & Ophir Frieder, 1998

2

Course Description

– This course will focus on topics related to database design. The course will begin with a brief review of modeling, and then discuss the evolution of the resulting products (e.g., the data models) into an actual design. This will include normalization, de-normalization, logical and physical design, and a variety of other topics that have design implications (VLDBs, data warehousing, OLTP, OLAP, Data Mining, RAID, etc).

Page 3: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Copyright, Harris Corporation & Ophir Frieder, 1998

3

Course Topics

• Basic data modeling concepts:– Entities, attributes, relationships, dependencies.

• Logical and physical database design:– Normal forms, normalization, object (i.e., table and index) placement.

• Design configurations:– On-line transaction processing, decision support, data warehousing,

VLDBs.

Note that this course will not attempt to present a process, but will rather focus on a variety of common database problems and issues.

Page 4: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Copyright, Harris Corporation & Ophir Frieder, 1998

4

Course Outline

– Introduction

– Modeling & Design Overview

– Normal Forms

– Normalization

– Logical & Physical Design (Object Placement)

– Data Warehousing & VLDBs

– De-normalization

– RAID

Page 5: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Copyright, Harris Corporation & Ophir Frieder, 1998

5

What Is Data Modeling?

Information modeling is a technique that supports many of the activities needed to manage information as an asset.

Information modeling is a technique for describing information structures.

-Designing Quality Databases with IDEF1X Information Models by Thomas A. Bruce.

Page 6: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Copyright, Harris Corporation & Ophir Frieder, 1998

6

Data ModelingLanguages & Processes

• Relational Based:– IDEF1X

– Chen

– Information Engineering

– NIAM

– MERISE

• Others:– Bachman

– Associative Data Modeling

– Semantic Information Modeling

– IBM’s Repository Modeling Language

Page 7: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Copyright, Harris Corporation & Ophir Frieder, 1998

7

Data ModelingProducts

• Relational modeling typically defines:– Entities

– Attributes

– Keys (candidate, primary, foreign, alternate, secondary)

– Relationships (cardinality, type)

• The above are summarized in a variety of different types of diagrams:– Entity relationship diagram

– Key based model

– Project information model

– Fully attributed model

– Transformation model

– Enterprise model

Page 8: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

8

Example - Video Store Model*

OVERDUE-NOTICE

customer-number (FK)movie-number (FK)movie-copy-number (FK)rental-record-date(FK)notice-date

notice-textemployee-number (FK)

movie-number

movie-name (IE1)movie-ratingmovie-rental-rate

MOVIEMOVIE-COPY

movie-number (FK)movie-copy-number

remaining-lifegeneral-condition

customer-number

customer-name (IE1)customer-status-codecustomer-address

CUSTOMER

MOVIE-RENTAL-RECORD

customer-number (FK)movie-number (FK)movie-copy-number (FK)rental-record-date

rental-datedue-daterental-statuspayment-amountpayment-datepayment-statusoverdue-charge

RECORD-INVOLVEMENT

customer-number (FK)movie-number (FK)movie-copy-number (FK)rental-record-date(FK)employee-number (FK)involvement-timestamp

involvement-type

employee-number

employee-name (IE1)hire-datesalaryemployee-address

EMPLOYEE

is in stock as

borrows under

is rented under

has involvement ofis involved with

listed on

may receive

P

P

P

*Thomas A. Bruce, Designing Quality Databases with IDEF1X Information Models, Figure 4.1, p. 74. Copyright © 1992 by Thomas A. Bruce. Reprinted by permission of Dorset House Publishing, 353 W. 12 St., New York, N.Y. 10014. All rights reserved.

Page 9: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Copyright, Harris Corporation & Ophir Frieder, 1998

9

Data ModelingTools

Power Designer - Sybase

Designer 2000 - Oracle

ER/Studio - Embarcadero

ERwin - Logic Works

Data Modeler - Iconix

Visio Professional - Visio Corporation

Vivid Clarity - Intek Technologies

EasyER/EasyObject - Visible Systems

And the list goes on...see www.dbmsmag.com/pccase.shtml

Page 10: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Copyright, Harris Corporation & Ophir Frieder, 1998

10

Database Design

• Database design decisions made during modeling phases:– Selection of entities, attributes, relationships, etc.,

• Such decisions have a direct impact on database design:– Entities => tables

– Attributes => columns

– Search Keys => indices

– Relationships => triggers, referential constraints

• Many design decisions are not made during modeling:

– De-normalization

– Index selection

– Object placement

Page 11: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Copyright, Harris Corporation & Ophir Frieder, 1998

11

Components Of ADatabase Design

• Tables– columns (type, constraints)

– keys (primary, foreign)

– triggers

• Indices– column selection

– column index order

– index type (clustered, nonclustered, hashed, bitmap)

• Object Placement– index placement

– table placement

• Device Configuration– mirroring

– striping

Page 12: Copyright, Harris Corporation & Ophir Frieder, 19981 Database Design.

Copyright, Harris Corporation & Ophir Frieder, 1998

12

Course Focus

• Problems and issues that arise throughout the database life-cycle, from modeling to administration.

• Topics considered will have direct implications for database design.

• All discussion will be in the context of the relational model (as opposed to the network, hierarchical, or object-oriented models).