Sfrgttk

How can I introduce myself to a party without saying that I am a rogue?

How do you enable SQL Server 2019's result set caching?

Do authors have to be politically correct in article-writing?

I am on the US no-fly list. What can I do in order to be allowed on flights which go through US airspace?

Emit zero-width bash prompt sequence from external binary

How to acknowledge an embarrassing job interview, now that I work directly with the interviewer?

raspberry pi change directory (cd) command not working with USB drive

If all harmonics are generated by plucking, how does a guitar string produce a pure frequency sound?

Metadata API deployments are failing in Spring '19

Why didn't Eru and/or the Valar intervene when Sauron corrupted Númenor?

4 Spheres all touching each other??

Is my plan for fixing my water heater leak bad?

Do commercial flights continue with an engine out?

Why can I easily sing or whistle a tune I've just heard, but not as easily reproduce it on an instrument?

What is the wife of a henpecked husband called?

Why is this code uniquely decodable?

Cyclical Argument in Plato's Phaedo

Can a person refuse a presidential pardon?

What is better: yes / no radio, or simple checkbox?

How do we edit a novel that's written by several people?

What happens if a wizard reaches level 20 but has no 3rd-level spells that they can use with the Signature Spells feature?

What is the purpose of easy combat scenarios that don't need resource expenditure?

How to roast potatoes in the oven to make them crispy?

ip vs ifconfig commands pros and cons

Kimball Data: Modeling Data as Both Fact and Dimension with View

Datawarehouse Design: Combined Date Time dimension vs. Separate Day and Time dimensions and timezonesData modeling membership and profileshow many fact tables do I need given I want to build an OLAP for Quotation Line Item and Purchase Order Line Item report?Time dimension or timestamp in fact table?Non numeric attributes in fact table (to track data source)?Data Warehouse Design and Double DippingWhen to Converge Dimensions in a Data Warehouse When There Are Few Common AttributesData Warehouse vs Data Mart vs database (separating logic from hardware)Is the modeling technique changing with column-oriented databases?Data Warehouse: Can a Transaction Table also be a Dimension?

0

In Data warehousing, Kimball discusses modeling an insurance policy premium as Both Dimension and Fact.
I have the following table,

create table dbo.DimAutoInsurance

(

    DimAutoInsuranceId int primary key identity(1,1),

    CustomerName varchar(100),

    CustomerAddress varchar(255),

    PolicyCoverageAmount numeric (15,2), 

    PolicyBeginDate datetime,

    PolicyExpirationDate datetime

)

For the Fact table, should I reconduct ETL another table for fact? Copying the data again, would seem redundant.
Or should I create a view? What is best database design strategy?

create view dbo.FactAutoInsurance

as 

select

    DimAutoInsuranceId,

    PolicyCoverageAmount numeric (10,2), 

from dbo.DimAutoInsurance

https://www.kimballgroup.com/2007/12/design-tip-97-modeling-data-as-both-a-fact-and-dimension-attribute/

Kimball:
A more ambiguous example is the limit on a coverage within an automobile insurance policy. The limit is a numerical data item, say $300,000 for collision liability. Furthermore, many queries would group or constrain on this limit data item. This sounds like a slam dunk for the limit being an attribute of the coverage dimension.

One could pose some important queries summing or averaging all the limits on many policies and coverages. This sounds like a slam dunk for the limit being a numeric fact in a fact table.
Rather than agonizing over the dimension versus fact choice, simply model it BOTH ways! Include the limit in the coverage dimension so that it participates in the usual way as a target for constraints and the content for row headers, but also put the limit in the fact table so it can participate in the usual way within complex computations."

sql-server database-design data-warehouse sql-server-2017

share

asked 2 mins ago

Joe Smith 8435Joe Smith 8435

665

add a comment | 

0

In Data warehousing, Kimball discusses modeling an insurance policy premium as Both Dimension and Fact.
I have the following table,

create table dbo.DimAutoInsurance

(

    DimAutoInsuranceId int primary key identity(1,1),

    CustomerName varchar(100),

    CustomerAddress varchar(255),

    PolicyCoverageAmount numeric (15,2), 

    PolicyBeginDate datetime,

    PolicyExpirationDate datetime

)

For the Fact table, should I reconduct ETL another table for fact? Copying the data again, would seem redundant.
Or should I create a view? What is best database design strategy?

create view dbo.FactAutoInsurance

as 

select

    DimAutoInsuranceId,

    PolicyCoverageAmount numeric (10,2), 

from dbo.DimAutoInsurance

https://www.kimballgroup.com/2007/12/design-tip-97-modeling-data-as-both-a-fact-and-dimension-attribute/

Kimball:
A more ambiguous example is the limit on a coverage within an automobile insurance policy. The limit is a numerical data item, say $300,000 for collision liability. Furthermore, many queries would group or constrain on this limit data item. This sounds like a slam dunk for the limit being an attribute of the coverage dimension.

One could pose some important queries summing or averaging all the limits on many policies and coverages. This sounds like a slam dunk for the limit being a numeric fact in a fact table.
Rather than agonizing over the dimension versus fact choice, simply model it BOTH ways! Include the limit in the coverage dimension so that it participates in the usual way as a target for constraints and the content for row headers, but also put the limit in the fact table so it can participate in the usual way within complex computations."

sql-server database-design data-warehouse sql-server-2017

share

asked 2 mins ago

Joe Smith 8435Joe Smith 8435

665

add a comment | 

In Data warehousing, Kimball discusses modeling an insurance policy premium as Both Dimension and Fact.
I have the following table,

create table dbo.DimAutoInsurance

(

    DimAutoInsuranceId int primary key identity(1,1),

    CustomerName varchar(100),

    CustomerAddress varchar(255),

    PolicyCoverageAmount numeric (15,2), 

    PolicyBeginDate datetime,

    PolicyExpirationDate datetime

)

For the Fact table, should I reconduct ETL another table for fact? Copying the data again, would seem redundant.
Or should I create a view? What is best database design strategy?

create view dbo.FactAutoInsurance

as 

select

    DimAutoInsuranceId,

    PolicyCoverageAmount numeric (10,2), 

from dbo.DimAutoInsurance

https://www.kimballgroup.com/2007/12/design-tip-97-modeling-data-as-both-a-fact-and-dimension-attribute/

Kimball:
A more ambiguous example is the limit on a coverage within an automobile insurance policy. The limit is a numerical data item, say $300,000 for collision liability. Furthermore, many queries would group or constrain on this limit data item. This sounds like a slam dunk for the limit being an attribute of the coverage dimension.

One could pose some important queries summing or averaging all the limits on many policies and coverages. This sounds like a slam dunk for the limit being a numeric fact in a fact table.
Rather than agonizing over the dimension versus fact choice, simply model it BOTH ways! Include the limit in the coverage dimension so that it participates in the usual way as a target for constraints and the content for row headers, but also put the limit in the fact table so it can participate in the usual way within complex computations."

sql-server database-design data-warehouse sql-server-2017

share

asked 2 mins ago

Joe Smith 8435Joe Smith 8435

665

create table dbo.DimAutoInsurance

(

    DimAutoInsuranceId int primary key identity(1,1),

    CustomerName varchar(100),

    CustomerAddress varchar(255),

    PolicyCoverageAmount numeric (15,2), 

    PolicyBeginDate datetime,

    PolicyExpirationDate datetime

)

create view dbo.FactAutoInsurance

as 

select

    DimAutoInsuranceId,

    PolicyCoverageAmount numeric (10,2), 

from dbo.DimAutoInsurance

share

asked 2 mins ago

Joe Smith 8435Joe Smith 8435

665

share

asked 2 mins ago

Joe Smith 8435Joe Smith 8435

665

asked 2 mins ago

Joe Smith 8435Joe Smith 8435

665

asked 2 mins ago

Joe Smith 8435Joe Smith 8435

665