105 lines
5.5 KiB
Markdown
105 lines
5.5 KiB
Markdown
# Exam 2 - Queen Anne Curiosity Shop and Writer's Patrol
|
|
|
|
## Instructions
|
|
- Answer Questions A through G found on pages 187-189 in Chapter 3 for the Queen Anne Curiosity Shop.
|
|
- Answer Questions A through G found on pages 209-210 in Chapter 4 for the Queen Anne Curiosity Shop.
|
|
- Answer Questions A and B found on page 262 in Chapter 5 for the Writer's Patrol Case.
|
|
- Answer Questions A through E found on page 265 in Chapter 5 for the Queen Anne Curiosity Shop.
|
|
- Answer Questions A through E found on page 321 in Chapter 6 for the Queen Anne Curiosity Shop.
|
|
- Deliver a single sql file, along with a document that contains all the content from the sql file.
|
|
- Do not include the result table unless specifically directed to.
|
|
- Include at least one line of white space between answers.
|
|
|
|
## Questions A-G in Chapter 3
|
|
|
|
### Data
|
|
Figure 3.33: Typical Sales Data
|
|
|
|
|
|
Figure 3.34: Typical Purchase Data
|
|
|
|
|
|
### Questions
|
|
A.) Using these data, state assumptions about functional dependencies among the columns of data. Justify your assumptions on the basis of these sample data and also on the basis of what you know about retail sales.
|
|
|
|
B.) Given your assumptions in part A, comment on the appropriateness of the following designs:
|
|
1. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem, Price, Tax, Total)
|
|
2. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem, Price, Tax, Total)
|
|
3. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem, Price, Tax, Total)
|
|
4. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem, Price, Tax, Total)
|
|
5. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem, Price, Tax, Total)
|
|
6. CUSTOMER (LastName, FirstName, Phone, EmailAddress)
|
|
and
|
|
SALE (InvoiceDate, InvoiceItem, Price, Tax, Total)
|
|
7. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate)
|
|
and
|
|
SALE (InvoiceDate, InvoiceItem, Price, Tax, Total)
|
|
8. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem)
|
|
and
|
|
SALE (InvoiceDate, InvoiceItem, Price, Tax, Total)
|
|
|
|
C.) Modify what you consider to be the best design in part B to include surrogate ID columns called CustomerID and SaleID. How does this improve the design?
|
|
|
|
D.) Modify the design in part C by breaking SALE into two relations named SALE and SALE_ITEM. Modify columns and add columns as you think necessary. How does this improve the design?
|
|
|
|
E.) Given your assumptions, comment on the appropriateness of the following designs:
|
|
1. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor, Phone)
|
|
2. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor, Phone)
|
|
3. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor, Phone)
|
|
4. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor, Phone)
|
|
5. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate)
|
|
and
|
|
VENDOR (Vendor, Phone)
|
|
6. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor)
|
|
and
|
|
VENDOR (Vendor, Phone)
|
|
7. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor)
|
|
and
|
|
VENDOR (Vendor, Phone)
|
|
|
|
F.) Modify what you consider to be the best design in part E to include surrogate ID columns called PurchaseID and VendorID. How does this improve the design?
|
|
|
|
G.) The relations in your design from part D and part F are not connected. Modify the database design so that sales data and purchase data are related.
|
|
|
|
|
|
## Questions A-G in Chapter 4
|
|
|
|
### Question Information
|
|
The Queen Anne Curiosity Shop project questions in Chapter 3 asked you to create a set of relations to organize and link the Queen Anne Curiosity Shop typical sales data shown in Figure 3-33 and the typical purchase data shown in Figure 3-34. The set of relations may look similar the following, although some additional columns have been added to the CUSTOMER relation to more closely match the Queen Anne Curiosity Shop database schema shown in the Project Questions for Chapter 2:
|
|
|
|
- CUSTOMER (CustomerID, LastName, FirstName, EmailAddress, EncryptedPassword, Address, City, State, ZIP, Phone, ReferredBy)
|
|
- SALE (SaleID, CustomerID, InvoiceDate, PreTaxTotal, Tax, Total)
|
|
- SALE_ITEM (SaleID, SaleItemID, PurchaseID, SalePrice)
|
|
- PURCHASE (PurchaseID, PurchaseItem, PurchasePrice, PurchaseDate, VendorID)
|
|
- VENDOR (VendorID, Vendor, Phone)
|
|
|
|
Figure 4.1: Guidelines for Assessing Table Structure
|
|
|
|
|
|
### Questions
|
|
A.) Follow the procedure shown in Figure 4-1 to assess these data.
|
|
1. List all functional dependencies.
|
|
2. List any multivalued dependencies.
|
|
3. List all candidate keys.
|
|
4. List all primary keys.
|
|
5. List all foreign keys.
|
|
6. State any assumptions you make as you list these components.
|
|
|
|
B.) List questions you would ask the owners of the Queen Anne Curiosity Shop to verify your assumptions.
|
|
|
|
C.) If there are any multivalued dependencies, create the tables needed to eliminate these dependencies.
|
|
|
|
D.) Do these data have the multivalue, multicolumn problem? If so, how will you deal with it?
|
|
|
|
E.) Do these data have the inconsistent data problem? If so, how will you deal with it?
|
|
|
|
F.) Do these data have a null (missing) value data problem? If so, how will you deal with it?
|
|
|
|
G.) Do these data have the general-purpose remarks problem? If so, how will you deal with it?
|
|
|
|
## Questions A and B in Chapter 5
|
|
|
|
## Questions A-E in Chapter 5
|
|
|
|
## Questions A-E in Chapter 6
|