Re: ROLAP Dimension Question

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



The Analysis Server has its own caches -- including caches for calculations.
So if an attribute changes in the dimension table but Analysis Services
doesn't know about it, then you will not see the change reflected in your
queries until the next time AS decides to drop its caches.

But you should be able to do this explicitly by sending a ClearCache request
also... See:
http://msdn2.microsoft.com/en-us/library/ms187154.aspx


Note that some calculations are considered non-deterministic (e.g. a stored
proc or the VBA Now function, etc.) -- and will be re-calculated every time.
But most builtin functions and operations are deterministic and are
candidates for caching.

HTH,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Wendell G." <WendellG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AC827117-0C3A-48DD-B9A8-94AA98BFFDA0@xxxxxxxxxxxxxxxx
Explain this to me.

I have a Cube. The Cube, all of the Dimensions, Partitions - everything
is
set to Storage Mode = ROLAP. I have completely turned off
ProactiveCaching.

If a member gets added to one of my dimensions, it will not appear in my
Cube data until I reprocess the Cube. That I get.

I have a series of Time Dimensions that I have built based on an old model
found in the SQL Server BI Accelerator. My Time Dimensions include the
notion of Current Date, which is an attribute. All time-based Named Sets
for
determining Current Day, Week, Month, Year are based on this attribute.

When the Current Date value is changed in my underlying data, the change
is
not reflected in my OLAP cube. I have to reprocess the cube in order to
get
my time-based named sets to reflect the correct current time period.

Does this seem normal within the context of ROLAP storage? Why would
reprocessing be required in this situation? Wouldn't an attribute of a
ROLAP-based dimension get updated dynamically? Wouldn't any named-set
based
on this attribute also get updated dynamically?

Thanks in advance for your help.

--
Wendell G.


.



Relevant Pages

  • Analysis Services Query Log Inconsistency
    ... Analysis Services 2000 allows up to 128 dimensions per cube; ... level in each dimension a particular query uses. ...
    (microsoft.public.sqlserver.olap)
  • Spoof shared dimension for virtual cube
    ... just getting back into Analysis Services again, ... Two cubes, ... Cube1 has 10 more dimensions, ... I'm sure it's possible to get this result with MDX (which I'm still not ...
    (microsoft.public.sqlserver.olap)
  • Re: dimensions and cube aggregs
    ... You might consider looking at the Analysis Services Performance Guide. ... > I have 8 dimensions that are needed for various queries. ... > I am trying to use them all in 1 cube, ... > The problem is the aggregations get a bit out of hand even at 20%. ...
    (microsoft.public.sqlserver.olap)
  • memory usage in SQL Server Analysis Services 2005 (SSAS)
    ... I am running the enterprise edition of Analysis services 2005. ... cube that has 4 dimensions and 2 years of test ... I was able to setup the cube and process around 43 million rows easily ... further and found that the CPU on the server spikes to 100% when I ...
    (microsoft.public.sqlserver.olap)
  • Re: Fairly Large Cube-Performance Improvement recommendations
    ... move) if the cube has large number of dimensions. ... We have 30 dims in the cube and the storage design wizard taked about 45 ... > 1) execute a fairly long query, let's say one that runs for 20 seconds. ...
    (microsoft.public.sqlserver.olap)