A Method for Data Warehouse Design - Data Warehouse Systems: Design and Implementation - page 398

Employee City

EmployeeID
FirstName
LastName
Title
BirthDate
HireDate
Address
City
Region
PostalCode
Country

CityName

Supplier

SupplierID
CompanyName
Address
PostalCode

State
StateName
EnglishStateName
StateType
StateCode
StateCapital

Customer

CustomerID
CompanyName
Address
PostalCode

Supervision
Subordinate

Region
RegionName
RegionCode

Time

Sales

Date
DayNbWeek
DayNameWeek
DayNbMonth
DayNbYear
WeekNbYear
Calendar

Quantity
UnitPrice: Avg +!
Discount: Avg +!
SalesAmount
Freight
/NetAmount

OrderDate

Country

DueDate

CountryName
CountryCode
CountryCapital
Population
Subdivision

ShippedDate

Month Product

MonthNumber
MonthName

ProductID
ProductName
QuantityPerUnit
UnitPrice
Discontinued

Continent

ContinentName

Quarter
Quarter

Categories

Shipper
ShipperID
CompanyName

Category

Semester

CategoryID
CategoryName
Description

Semester

Order

OrderNo
OrderLineNo

Year

Year

Fig. 10.7 Conceptual schema of the Northwind data warehouse (repeated from
Fig. 4.2 )

Also, following Table 10.1 , geographic data are transformed in dimension
levels, which are used in three hierarchies for the Customer , Supplier ,and
Employee dimensions. These hierarchies share the levels City , State , Region ,
Country ,and Continent and are manually constructed (using the external
data sources) taking into account the administrative divisions of the countries
we want to represent. In addition, the many-to-many relationship between
Employee and City defines a nonstrict hierarchy. This relationship was