Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Lots of small dimensions Expand / Collapse
Author
Message
Posted Friday, August 8, 2014 2:41 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, October 22, 2014 7:20 AM
Points: 79, Visits: 462
I have business process that we report on - Fitting room appointments. stores setup fitting rooms on their systems, book in appointments types on their calendar and assign staff to the fitting rooms to help with dress try-ons.

The dimensions for these are very simple ie. 3-4 columns max but have about 1000 rows each as the data for all the store. Is it over kill to go through the process creating staging and live tables and building etl packages to populate StoreUsers, AppointmentTypes and FittingRooms dimensions?

I thought about using a Junk dimension but if i understand there purpose correctly they would hold every combination of the the 3 tables possible.


Thanks
Post #1601071
Posted Wednesday, August 13, 2014 2:41 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 9:59 AM
Points: 2,126, Visits: 1,474
How were you thinking of populating your dimension tables without creating ETL packages? Whether you need to create staging tables depends on a number of things such as:

- how frequently your ETL process runs.
- how much data is captured form your source systems.
- what sort of resource pressure the ETL process places on your source systems. (Staging tables are often used for just the EL part of ETL, i.e. get the data out of the source systems as quickly as possible therefore minimising the impact on those source systems).
- do you have Slowly Changing Dimensions and if so, which type?

Another benefit of using staging tables is that in the event of a failure in loading data into your Data Warehouse, you don't have to back and extract data from the source systems again - you just go back to the staging tables.

It's perfectly possible and normal to have dimension tables with far less than 1000 rows.

Regards
Lempster
Post #1602617
Posted Wednesday, August 13, 2014 8:02 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, October 22, 2014 7:20 AM
Points: 79, Visits: 462
Hi

Thanks for the reply. When i say creating etl packages im really talking about complex ones with lookups, conditional splits derived colums inserts and updates etc. This business process im talking about is just one of a few processes, the rest of which properly use etl and staging tables for the exact reasons you mention i.e. load and scd.

Im new to DW so im just not sure if you have to create complex etl package and analyse scd's requierments on all data needed. or is it sufficient to just have an etl that drops and recreates the data in some dimensions for example for an appointment status dimension that only has 10 rows do you really need to create a complex package that track type 1 & 2 changes?
Post #1602743
Posted Thursday, August 14, 2014 2:48 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 9:59 AM
Points: 2,126, Visits: 1,474
Whether you need to track changes or not should stem from the business requirements regardless of how many rows are in a dimension table. During the dimensional modelling phase, those requirements need to be captured. Of course, the situation that often arises is that when asked the question 'do you need to track history for this attribute' the business will say 'yes' to everything!
This is why it is key for a DWH project to be successful that you really get your business users engaged in the process. Having a good Business Analyst on board can really help in that regard.

There is no definitive answer to your question, but hopefully what I've said helps a little bit...?

Regards
Lempster
Post #1603163
Posted Friday, August 15, 2014 6:44 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 10:09 AM
Points: 818, Visits: 2,075
Is it over kill to go through the process creating staging and live tables and building etl packages to populate StoreUsers, AppointmentTypes and FittingRooms dimensions?


No, it's not overkill. The ETL package(s) [some might disagree, but all three could be part of the same package] might not all have the same features that one for daily use would have, but you need something. It doesn't even have to be part of the automated download.



Post #1603680
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse