dbTalk Databases Forums  

Incremental Process - why do Dim updates query entire table?

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss Incremental Process - why do Dim updates query entire table? in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
lmcphee
 
Posts: n/a

Default Incremental Process - why do Dim updates query entire table? - 04-21-2006 , 06:49 AM






I am using AS2000 with SP4.

I have a cube which has been fully processed. I got the Max(ID) = 27199456
from the fact table and then executed a manual incremental process, giving
"ID > 28000000" as the filter expression. This filter excudes all rows, but I
was surprised to see that the queries to update the private dimensions did
NOT use the filter. So even though there was nothing to be done, the
processing still took a couple of minutes.

Why don't the dim updates use the filter expression?

So now I am considering complicating my DTS further by adding a SQL task to
retrieve the Max(ID) from the fact table and comparing to the Max ID of
records processed into the cube (stored in SQL after previous processing). If
the IDs are the same (i.e. no new events) then completely skip the cube
processing task. That should save me those 2 minutes.

Is there an easier way?

LMcPhee

Reply With Quote
  #2  
Old   
lmcphee
 
Posts: n/a

Default RE: Incremental Process - why do Dim updates query entire table? - 04-21-2006 , 11:13 AM






After a little reflection on this it occurred to me that there is no
guarantee that the dimension members were directly from the fact table, so
for AS to use the filter it would have to know how to join the fact table to
the source table for the dimension.

So I will manage this logic in the DTS myself.

LMcPhee

"lmcphee" wrote:

Quote:
I am using AS2000 with SP4.

I have a cube which has been fully processed. I got the Max(ID) = 27199456
from the fact table and then executed a manual incremental process, giving
"ID > 28000000" as the filter expression. This filter excudes all rows, but I
was surprised to see that the queries to update the private dimensions did
NOT use the filter. So even though there was nothing to be done, the
processing still took a couple of minutes.

Why don't the dim updates use the filter expression?

So now I am considering complicating my DTS further by adding a SQL task to
retrieve the Max(ID) from the fact table and comparing to the Max ID of
records processed into the cube (stored in SQL after previous processing). If
the IDs are the same (i.e. no new events) then completely skip the cube
processing task. That should save me those 2 minutes.

Is there an easier way?

LMcPhee

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.