All Powder Board and Ski Microsoft Access Workbook Chapter 2: Database Design Jerry Post Copyright...
-
Upload
eileen-murphy -
Category
Documents
-
view
212 -
download
0
Transcript of All Powder Board and Ski Microsoft Access Workbook Chapter 2: Database Design Jerry Post Copyright...
All Powder Board and Ski
Microsoft Access WorkbookChapter 2: Database DesignJerry PostCopyright © 2003
DBDesign: An Expert System
http://time-post.com/dbdesign Benefits
Makes it easy to create database diagrams Saves data in central location, so changes can be
made from almost any computer Provides immediate detailed feedback on the
design Requirements
Instructors must ask for a free account Instructors and students need a Java-enabled Web
browser
Access Data Types (Domains)Name Data Bytes
Text (characters) fixed variable memo
NATextMemo
255 64 K
VariableVariable
Numeric Byte (8 bits) Integer (16 bits) Long (32 bits) (64 bits) Fixed precision Float Double Currency Yes/No
Number: ByteNumber: IntegerNumber: Long IntegerNANumber: DecimalNumber: SingleNumber: DoubleCurrencyYes/No
0-255+/- 32767+/- 2 billion+/- 1 E 28+/- 1 E 38+/- 1 E 308+/- 900.0000 trillion0/1
124124881 bit
Date/Time Date/Time 1/1/100 – 12/31/9999 (1 sec) 8
Image OLE Object 1 gigabyte Variable
AutoNumber AutoNumber Long (+/- 2 billion) 4
Initial Business Objects
Employee
EmployeeIDTaxpayerIDLastNameFirstNameAddressCityStateZIP
Customer
CustomerIDLastNameFirstNamePhoneAddressCityStateZIP
Sale
SaleIDSaleDateCustomerIDEmployeeID
Rental
RentIDRentDateCustomerIDExpectedReturn
Associations or Relationships
Employee
EmployeeIDTaxpayerIDLastNameFirstNameAddressCityStateZIP
Customer
CustomerIDLastNameFirstNamePhoneAddressCityStateZIP
Sale
SaleIDSaleDateCustomerIDEmployeeID
Rental
RentIDRentDateCustomerIDExpectedReturn
0…*
1…1
Getting Started
Enter the key numbers you received
Create a username and password.
Enter your correct name, e-mail address and StudentID
Class Registration
Successful account creation
Select your university and class
Enter the admit code
DBDesign: Example
Available columns
Menu
Class(entity)
Corrections
Status line
Relationships
Drag-and-drop column
Select min and max for both sides of the relationship
Design Errors
Add SKU to the Sale table
Connect the Inventory table to the Sale table
Double click the diagnostic message
Possible errors are highlighted
More Errors
Try setting SKU as a key
It still causes problems because SaleDate does not depend on the SKU
Split Many-to-Many Relationship
Sale
SaleIDSaleDateCustomerIDEmployeeID
Inventory
SKUSizeQOH
Many-to-Many
SaleItem
SaleIDSKUQuantitySoldSalePrice
1…1
0…*
1…*
1…1
Ski Shop Inventory
Photo: www.rossignol.com
Ski shops carry multiple lengths of each ski or board model.
Model information refers to the overall type of board or ski.
Inventory information refers to an individual ski or board—defined by its length.
Model:Rossignol Axium
Item: 196 cm Item: 181 cm
Models and Items
Customer Skill Level
CustomerID, LastName, … Style, SkillLevel
CustomerID, LastName, … Style, SkillLevel
Business rule: Each customer can have one skill in many styles.Business rule: Each style can apply to more than one customer.Need a table with both attributes as keys.
CustomerID, LastName, … Style, SkillLevel
But you cannot include LastName, FirstName and so on, because then you would have to re-enter that data for each customer skill.
Customer Style Skills
Customer
CustomerIDLastNameFirstNamePhoneAddressCityStateZIP
CustomerSkill
CustomerIDStyleSkillLevel
Style
StyleStyleDescription
SkillLevel
SkillLevelSkillDescription