Review Question #2)
1) Data C
2) Database Application B
3) Constraint L
4) Repository G
5) Metadata F
6) Data Warehouse M
7) Information A
8) User View J
9) Database Management System K
10) Data Independence H
11) Database E
12) Enterprise Resource Systems Planning I
13) Systems Development Life Cycle R
14) Prototyping O
15) Enterprise Data Model D
16) Conceptual Schema Q
17) Internal Schema P
18) External Schema N
Problems & Exercises:
1) Attached as a photo.
8a) One-to-many
8b) One-to-many
8c) There could be a relationship between the store and the customer.
11) Three additional entities for PVFC are Employee, Supplier, and Shipment. They are all valid because they represent important categories of data about the entities managed by the organization.
20a) The field size for the ProductLineName field in the Product table can range from 1-40 characters. Reason being that the SQL Create Table definition of ProductLineID field is set to 40 characters with a VARCHAR datatype.
20b) The ProductID field is set as NOT NULL. ProductID is required because it is the Primary Key of the table. (Primary Key fields cannot be empty or non existent).
20c) The FOREIGN KEY in the SQL statement reveals that the ProductLineID field in the Product_T table refers back to the ProductLineID primary key, which is stored in the ProductLine_T table.
21a) Sales to Date is calculated by multiplying the price by the quantity.
21b) If you remove “Home Office” from the Criteria Line under ProductLineName, all product lines would show instead of just the Home Office line.
22a) These will be needed: Customer, Payment, Order, Invoice, Order Line, Product.
22b) Customer, Payment, Order, Invoice, Order Line, Product (all entities) will be needed for the SQL query.Assignment #1, 11th Edition
Review Question #2)
1) Data C
2) Database Application B
3) Constraint L
4) Repository G
5) Metadata F
6) Data Warehouse M
7)