Chapter 8 T/F
16) The relational model is the only way through which dimensionally modeled databases can be implemented.
F
2) A dimensional model cannot be based on a single source.
F
21) The STATEWIDE HEALTH star schema contains the dimension PRESCRIPTION.
F
22) The detailed fact table in the STATEWIDE HEALTH star schema is a line-item detailed fact table.
F
26) The STATEWIDE HEALTH PRESCRIPTIONS database column PrescQuantity provides the data for a dimension in the STATEWIDE HEALTH star schema.
F
27) The STATEWIDE HEALTH PRESCRIPTIONS database column MedicationDosage provides the data for the fact table in the STATEWIDE HEALTH star schema.
F
12) Independent data marts approach can be used for designing an enterprise-wide analytical data warehouse.
F
23) The STATEWIDE HEALTH PRESCRIPTIONS database column DoctorSpecialty provides the data for a dimension in the STATEWIDE HEALTH star schema.
T
5) All sources for a dimensional model must be operational data sources from the company that is building the dimensional model.
F
8) Aggregated fact tables have a finer level of granularity than detailed tables.
F
9) When a data warehouse is normalized, its dependent data marts also must be normalized.
F
11) Dimensionally modeled data warehouse approach can be used for designing an enterprise-wide analytical data warehouse.
T
15) Independent data marts approach results in multiple unrelated ETL infrastructures.
T
18) The STATEWIDE HEALTH star schema contains the dimension PATIENT.
T
19) The STATEWIDE HEALTH star schema contains the dimension DOCTOR.
T
20) The STATEWIDE HEALTH star schema contains the dimension MEDICATION.
T
36) The CUSTOM SPA DAILY VISITS DATABASE column ProcedureName provides the data for a dimension in the STATEWIDE HEALTH star schema.
T
37) The CUSTOM SPA DAILY VISITS DATABASE column SEYearOfHire provides the data for a dimension in the STATEWIDE HEALTH star schema.
T
4) Analytical queries on the dimensionally modeled database can be significantly simpler to create than on the equivalent nondimensional database.
T
35) The CUSTOM SPA DAILY VISITS DATABASE column PatronZip provides the data for a dimension in the STATEWIDE HEALTH star schema.
T
1) Dimensional modeling can be employed as a relational data modeling technique.
T
13) Normalized data warehouse approach results in multiple unrelated ETL infrastructures.
F
14) Dimensionally modeled data warehouse approach results in multiple unrelated ETL infrastructures.
F
10) Normalized data warehouse approach can be used for designing an enterprise-wide analytical data warehouse.
T
30) The CUSTOM SPA star schema contains the dimension PATRON.
T
28) The STATEWIDE HEALTH PRESCRIPTIONS database column PrescID provides the data for a dimension in the STATEWIDE HEALTH star schema.
F
3) In addition to giving each record of a dimension a new value that serves as a primary key within the dimensional model instead of the operational key value, surrogate key values contain additional information about each record in the dimension.
F
33) The CUSTOM SPA star schema contains the dimension VISIT.
F
34) The CUSTOM SPA star schema contains the dimension VISITPROCEDURE.
F
38) The CUSTOM SPA DAILY VISITS DATABASE column AmountCharged provides the data for a dimension in the STATEWIDE HEALTH star schema.
F
39) The CUSTOM SPA DAILY VISITS DATABASE column VisitID provides the data for a dimension in the STATEWIDE HEALTH star schema.
F
40) The CUSTOM SPA DAILY VISITS DATABASE column VisitTimeOfDay provides the data for a dimension in the STATEWIDE HEALTH star schema.
F
17) The ER modeling and dimensional modeling methods cannot be combined and used within the same data warehousing project.
F STATEWIDE HEALTH The following questions citing STATEWIDE HEALTH assume that a single-source star schema is created. The purpose of this star schema is to analyze quantities of prescribed medications by all dimensions provided by its source: the STATEWIDE HEALTH PRESCRIPTIONS DATABASE shown below. In this database, each prescription is prescribed for one patient by one doctor, and it contains one medication. STATEWIDE HEALTH PRESCRIPTIONS DATABASE PATIENT PatientID PatientName PatientWeight P11 Jim 160lb P22 Mary 125lb P33 Fred 250lb DOCTOR SPECIALTY DoctorID DoctorName Specialty SpecialtyID SpecialtyName D11 Lee S1 S1 Family Medicine D11 Hank S1 S2 Internal Medicine D33 Luisa S2 MEDICATION MedicationID MedicationName Dosage M11 Zolex 2mg M22 Luneva 1mg M33 Luneva 2mg PRESCRIPTION PrescID Patient Doctor PrescDate PrescTimeOfDay PrescMedication PrescQty RX11 P11 D11 1/1/2013 8:00 a.m. M11 12 RX22 P22 D22 1/1/2013 8:30 a.m. M22 10 RX33 P22 D22 1/1/2013 8:30 a.m. M11 20 RX44 P33 D11 1/1/2013 8:00 a.m. M11 10 RX55 P33 D33 1/2/2013 9:00 a.m. M33 30
24) The STATEWIDE HEALTH PRESCRIPTIONS database column MedicationName provides the data for a dimension in the STATEWIDE HEALTH star schema.
T
25) The STATEWIDE HEALTH PRESCRIPTIONS database column PatientWeight provides the data for a dimension in the STATEWIDE HEALTH star schema.
T
31) The CUSTOM SPA star schema contains the dimension SPAEMPLOYEE.
T
32) The CUSTOM SPA star schema contains the dimension PROCEDURE.
T
6) Transaction time is typically included as a column in the fact table.
T
7) A dimensional model can contain more than one fact table.
T
29) The STATEWIDE HEALTH PRESCRIPTIONS database column PrescTimeOfDay provides the data for a dimension in the STATEWIDE HEALTH star schema.
F CUSTOM SPA The following questions citing CUSTOM SPA assume that a single-source star schema is created. The purpose of this star schema is to analyze procedure revenue by all dimensions provided by its source: the CUSTOM SPA DAILY VISITS DATABASE, shown below. In this database, each visit includes one patron, one spa employee, and one or more procedures. The price for each procedure varies from visit to visit. CUSTOM SPA DAILY VISITS DATABASE PATRON PatronID PatronName PatronZip PT1 Daisy 60611 PT2 Ellena 60650 PT3 Nelly 60611 PT4 Marcia 60650 SPAEMPLOYEE SEID SEName SEYearOfHire SE1 Claire 2000 SE2 Jamie 2008 PROCEDURE ProcedureID ProcedureName PR1 Mani PR2 Pedi PR3 Massage VISIT VisitID Patron SEmployee VisitDate VisitTimeOfDay V1 PT1 SE1 1/1/2013 8:00 a.m. V2 PT2 SE2 1/2/2013 8:30 a.m. V3 PT3 SE1 1/3/2013 8:30 a.m. V4 PT1 SE2 1/3/2013 8:00 a.m. V5 PT4 SE1 1/4/2013 8:00 a.m. VISITPROCEDURES VisitID ProcedureID AmountCharged V1 PR1 $20 V1 PR2 $30 V2 PR1 $25 V3 PR2 $35 V4 PR3 $100 V5 PR1 $15 V5 PR2 $20 V5 PR3 $80