SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Designing a new factTable


Designing a new factTable

Author
Message
Michael Torsson
Michael Torsson
Valued Member
Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)

Group: General Forum Members
Points: 63 Visits: 316
Hi

I have a factTable that is filling up with appr. 500' rows every day and holds now 100'' rows. There are around 25 dimensions to this facttable. We now need to apply additional transformations on that data for some new reports without changing the existing model. There are a couple of new dimensions that needs to be addeed for the transformations and reports.

The analysis is made with Cubes and the Reports doesn't have to render in 2 seconds :-).
My dilemma is if we should store the new factTable with the complete set of dimensions from the old one + the new dimensions or just with a key from the old one.
The transormations can lead to many new rows.

1. New factTable with 25+5 Dimensions
Or
2. New FactTable with OldFactTableKey + 5 dimensions

The cube can have a view with joined facttables, point for solution 2.
History does not have to be added in the new facttable, point for solution 1

Regards
Mike
Koen Verbeeck
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27091 Visits: 13268
Do these new dimensions change the grain of the fact table?


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
Michael Torsson
Michael Torsson
Valued Member
Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)

Group: General Forum Members
Points: 63 Visits: 316
Hi Koen

With the new dimensions it is possible that the transformations will change the grain.

Mike
Koen Verbeeck
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27091 Visits: 13268
Personally I would go for option 1. I don't really like keys to other fact tables in the design.
And I would add the entire history in the new fact table, if possible. That way your old fact table is just a rollup of the new fact table.


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
xsevensinzx
xsevensinzx
SSCommitted
SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)

Group: General Forum Members
Points: 1992 Visits: 2696
I never touch the data source if I don't have too. I would make the new fact with a copy of the existing dimensions plus the addition of the new dimensions. This is what they coin as your data mart (mini-data warehouse) that can be completely conformed/tailored to your new business needs and can also be repopulated in the event of rapture.

Just my 2 cents.
Michael Torsson
Michael Torsson
Valued Member
Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)

Group: General Forum Members
Points: 63 Visits: 316
Thanks for your input.
To keep them apart is the best way to go forward in case of reloading failure etc.

/Michael
azhar.iqbal499
azhar.iqbal499
Old Hand
Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)

Group: General Forum Members
Points: 314 Visits: 525
To implement a new Fact table, You need to maintain loading process twice, I think you should attach new dimensions with existing fact Table if you convince your Lead other wise option 1 in better.
aaron.reese
aaron.reese
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1031 Visits: 902
Fact tables should stand alone. Dimensions can be shared between fact tables.

Create a new fact table with all the information required for the new process. If necessary, seed it by copying the existing fact table history into it.

This defines the difference between your Data Warehouse (where all the data is kept) and the Data-Mart (the data that the specific user requires in the format they require it)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search