Database Reference
In-Depth Information
SaleItemID
ItemID
SaleID
ItemPrice
1
1
1
$3,000.00
1
2
2
$500.00
2
1
3
$1,000.00
3
1
4
$50.00
4
1
5
$45.00
5
1
6
$250.00
7
$750.00
6
1
$250.00
7
1
8
8
1
9
$1,250.00
8
2
10
$1,750.00
9
1
11
$350.00
10
1
19
$5,000.00
10
2
21
$8,500.00
10
3
22
$750.00
17
$250.00
11
1
12
1
24
$50.00
13
1
20
$4,500.00
14
1
12
$3,200.00
Figure 7-48
Sample Data for the QaCS
SaLE_ItEM table
14
2
14
$475.00
15
1
23
$800.00
Suppose that you have designed a database for Morgan Importing that has the
following tables:
EMPLOYEE (
EmployeeID
, LastName, FirstName, Department, Phone, Fax,
EmailAddress)
STORE (
StoreName
, City, Country, Phone, Fax, EmailAddress, Contact)
ITEM (
ItemID
,
StoreName
,
PurchasingAgentID
, PurchaseDate, ItemDescription,
Category, PriceUSD)
SHIPPER (
ShipperID
, ShipperName, Phone, Fax, EmailAddress, Contact)
SHIPMENT (
ShipmentID
,
ShipperID, PurchasingAgentID
, ShipperInvoiceNumber,
Origin, Destination, ScheduledDepartureDate, ActualDepartureDate,
EstimatedArrivalDate)
SHIPMENT_ITEM (
ShipmentID
,
ShipmentItemID
,
ItemID
, InsuredValue)
SHIPMENT_RECEIPT (
ReceiptNumber
,
ShipmentID, ItemID, ReceivingAgentID
,
ReceiptDate, ReceiptTime, ReceiptQuantity, isReceivedUndamaged, DamageNotes)
A.
Do you think STORE should have a surrogate key? If so, create it and make required
adjustments in the design. If not, explain why not or make any other adjustments to
STORE and other tables that you think are appropriate.
B.
Specify NULL/NOT NULL constraints for each table column.
C.
Specify alternate keys, if any.
Search WWH ::
Custom Search