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

How to handle historical data change in SSAS Expand / Collapse
Author
Message
Posted Friday, February 15, 2013 9:07 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, December 8, 2014 8:33 PM
Points: 188, Visits: 376
I am a novice to SSAS and I was wondering if there is a way to process historical data change in a fact table? Time to time we do need to make adjustment to the data that was loaded to warehouse. In stead of doing full process, is there a way for SSAS to recognize the only updated info and process? Any help on this would be appreciated.
Post #1420611
Posted Monday, February 25, 2013 3:07 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, December 18, 2014 1:23 AM
Points: 739, Visits: 848
What is the database that you are looking at. If SQL Server then possibly CDC(change data capture) could be of interest? That would identify the changes.

Then process update could avoid a full process (depending on what changed).

E

Post #1423518
Posted Monday, February 25, 2013 7:57 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, December 8, 2014 8:33 PM
Points: 188, Visits: 376
We have a process to identify the changes, but I am more curious about how to process incrementally if the data is altered was 2 weeks old data or older(cloud be any historical date range) entry in fact table. Any help would be appreciated.
Post #1423620
Posted Monday, February 25, 2013 8:08 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, December 18, 2014 1:23 AM
Points: 739, Visits: 848
[url=http://technet.microsoft.com/en-us/library/ms174774.aspx][/url]

This location documents the processing options for Analysis Services objects. Have a good read through and see what will work for you. If it is historical data how regularly are you going to update it? Would splitting the cube into different partitions help?


E

Post #1423629
Posted Tuesday, February 26, 2013 7:53 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: 2 days ago @ 2:54 PM
Points: 820, Visits: 2,135
It sounds like your fact table is an accumulating snapshot. So snless the cube is split into partitions, and you can be certain that all the changes are in certain partitions, you will have to do a full process. Is the time so long that this is unrealistic. Mine have millions of rows and compile in about 10 minutes, but I can easily imagine that this might be small compared to others.


Post #1424090
Posted Friday, May 17, 2013 3:46 PM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: 2 days ago @ 6:42 PM
Points: 459, Visits: 1,065
How you define your partition is partly if not fully influenced by business logic. If a sale has a 30 day return period then you can create each partition in monthly increments more or less. You just process the affected partition rather than the entire cube.

I think the process update only works on dimensions, or am I wrong?

thanks.
Post #1454202
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse