You are designing a star schema for a dataset that contains records of online orders. Each record includes an order date, an order due date, and an order ship date. You need to ensure that the design

Question

Exhibit

Options

• ACreate a date dimension table that has a DateTime key.
• BCreate a date dimension table that has an integer key in the format of YYYYMMDD.
• CUse built-in SQL functions to extract date attributes.
• DUse integer columns for the date fields.
• EUse DateTime columns for the date fields.

• A
  25% (13)
• B
  59% (30)
• C
  6% (3)
• E
  10% (5)

Explanation

Why use a Date Dimension Table in a Data Warehouse. The Date dimension is one of these dimension tables related to the Fact. Here is a simple Data Diagram for a Data Mart of Internet Sales information for the Adventure Works DW database which can be obtained for free from CodePlex or other online sources. The relationship is created by the surrogate keys columns (integer data type) rather than the date The query users have to write against a Data Mart are much simpler than against a transaction database. There are less joins because of the one to many relationships between the fact dimension table(s). The dimension tables are confusing to someone who has been normalizing databases as a career. The dimension is a flattened or de-normalized table. This creates cases of duplicate data, but the simplistic query overrides the duplicate data in a dimensional model. analysis-services/ https://community.idera.com/database-tools/blog/b/community_blog/posts/why-use-a-date- dimension-table-in-a-data-warehouse

No community discussion yet for this question.