Handling early arriving facts
How do we handle early arriving facts? If you are an experienced DW developer you would have come across this many times, if you are a novice you are certain to face this challenge in the near future. Each organisation makes decision to handle this scenario as suited to them. I have handled this scenario in one of these 3 categories.
1. Ignore early arriving facts all together? Is that the right way to do it?
2. During load process populate the dimension table with the Natural Key and default values and map surrogate key to the incoming fact record.
3. During fact load map default surrogate key and load those records into the “Rejected” table.
I would be conducting a demo for point 2 and 3.
In depth analysis on what happens to the records in the Rejected table and what do I propose to resolve these records?
What is Business Intelligence Service Centre (BISC) and their involvement is going to mission critical for the success of your BI project?
I have been working with SQL Server for last 11 years. Predominantly I spent most of my carrier building data warehouses and loading the data using various ETL Tools such as DTS, SSIS, Ab-Initio and Informatica. I have work for well known brands such as Tyco and Reuters before joining Hitachi Consulting. I have got MBA in Project Management, MCITP-BI (2005 & 2008) & MCDBA. I have worked in diverse business sectors such as Financial Services, Media, Share Market Data, Mergers and Acquisition, Pub Management, Security, Building Society, Bank, Mortgages, Publishing and Commercial Finance.
The video is not available to view online.
- Session Files Explorer
The network name cannot be found.