dbTalk Databases Forums  

Incremental update of dimension results in #ERR

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


Discuss Incremental update of dimension results in #ERR in the microsoft.public.sqlserver.olap forum.



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

Default Incremental update of dimension results in #ERR - 04-06-2004 , 03:27 PM






I have a pretty large set of OLAP databases with quite a few daily
partitions in which more recently (apparently due to the size), when I
incrementally update the shared dimensions, for a short while after any MDX
queries result in #ERR. After waiting a 1/2 an hour or so, the same MDX
query comes back fine.

It appears that this may be due to the lazy aggregations processing -
normally, this isn't supposed to have any effect, but appears that it does
now (as per the reference:
http://msdn.microsoft.com/library/de...sions_55rn.asp,
where once dimensions are incrementally updated, the cubes that include the
dimension are refreshed automatically - both tasks are not supposed to
affect end-user access).

In trying to debug this, I have also updated the registry key for
ProcessAheadSegmentSize to insure that it is >70% of physical memory (along
with the high memory limit and other settings). Saying this, does any one
have any additional ideas how to resolve this?

Closest thing to a support reference I have found so far is:
http://support.microsoft.com/default.aspx?kbid=820358
Quote:
Utilize "FullReaggregate" option for processing included in AS2k SP3
TIA,
Denny




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.