Re: SSAS2005 - When do partitions need to be processed?

My guess here is that it is not aggregations but rather indexes being
processed.

I would suggest running Profiler against the server during processing and
seeing the events there -- the events for the partition should be for
ProcessIndex...

The actual processing of partitions doesn't appear to be significant here
though. It shows as:

Processing Cube 'Sales Current' completed successfully.
Start time: 5/12/2006 3:41:58 PM; End time: 5/12/2006 3:42:57 PM;
Duration: 0:00:59

Also, are you doing ProcessUpdate on all the dimensions in one operation
(using Batch/Parallel)? This would unify the cube processing into the same
transaction so that it only needs to happen once instead of repeated for
each of the dimensions.

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.

"Darren Gosbell" <jam@xxxxxxxxxxxxxxxxx> wrote in message
news:MPG.1ed32ff1a7122d298991a@xxxxxxxxxxxxxxxxxxxxx
This behaviour could be depend on whether your dimension has flexible or
rigid attribute relationships. BOL did not have a very succinct
definition, but the following is from one of the tutorials:


...you can specify that the relationship is either flexible or rigid. If
you define a relationship as rigid, Analysis Services retains
aggregations when the dimension is updated. If a relationship that is
defined as rigid actually changes, Analysis Services generates an error
during processing unless the dimension is fully processed


Time inherently has rigid relationships (you can't change which month a
particular date belongs to). But I believe all other dimension default
to flexible relationships which would mean that processing them would
result in all the aggregations (not the leaf level data) being dropped
and re-processed.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <#DAflH9dGHA.564@xxxxxxxxxxxxxxxxxxxx>, willgart@xxxxxxxxxxx
says...
generally a reprocess is required when there is a change in a hierarchy.
for example, if an employee is in New York and change to Boston, then the
hierarchy changes which required a process of the cubes to recalculates
the
aggregations correctly.
Changing a label (like the name of the customer) required only a simple
update (if the key column is not the same as the label column).

if you anticipate this type of changing, you have to use the slow
changing
feature in the dimension. I have not use it in AS2005 but in AS2000 yes.
this option will slow down accesses to the cubes because the system will
keep only aggregates at the top (all member) and bottom levels (the
employee)
intermediate levels are recalculate when asked by the user.
So when a employee change, there is no need to reprocess the cubes
because
the aggregation for boston and new york are not stored on the disk.

With AS2005 there is a proactive caching option at the dimension level,
but
I have not use it, if this caching works like in a cube... this could
help
you by reaggregate data when a table in the database change.

take a close look at the proactive caching features.

"Jesse O." <jesperzz@xxxxxxxxxxx> wrote in message
news:uN%233so8dGHA.4108@xxxxxxxxxxxxxxxxxxxxxxx
No, no slice set. We're using MOLAP. Thanks for your suggestion of
proactive caching.

I'm still confused as to why some dimensions process partitions while
others don't.

Perhaps someone from MS could chime in?

TIA.

Jesse.


"Jeje" <willgart@xxxxxxxxxxx> wrote in message
news:Ocp0ODrdGHA.4532@xxxxxxxxxxxxxxxxxxxxxxx
well...

when you create partitions, do you associate this partition to a
specific
slice of the cube?

use realtime partitions and the proactive caching feature. and/or
incremental processing.

I have seen a webcast where a billion rows database and the associated
cubes are updated in realtime.
The cache of the cube himself is updated, this mean that adding new


.

Relevant Pages

  • Re: SSAS2005 - When do partitions need to be processed?
    ... InsertCubeProcessingLog("Process Dimension All End", 1, 1, BeginTime, Now, ... The actual processing of partitions doesn't appear to be significant here ... Processing Cube 'Sales Current' completed successfully. ... With AS2005 there is a proactive caching option at the dimension level, ...
    (microsoft.public.sqlserver.olap)
  • Re: SSAS2005 - When do partitions need to be processed?
    ... InsertCubeProcessingLog("Process Dimension All Begin", 1, 0, BeginTime, Now, ... The actual processing of partitions doesn't appear to be significant here ... Processing Cube 'Sales Current' completed successfully. ... With AS2005 there is a proactive caching option at the dimension level, ...
    (microsoft.public.sqlserver.olap)
  • Re: long processing time
    ... currently it is processing 2 partitions in parallel. ... >1) Have you ran the Optimize Schema wizard in the Cube ... >the RDBMS (SQL Server or Oracle), ... >> The cube which took 9 days to process has time dimension ...
    (microsoft.public.sqlserver.olap)
  • Re: distinct count through calculated measure = slow client process...
    ... I have 2 dcount measures in test: ... I presume I have to aggregate the time dimension at the month level to ... What's appends if I optimize to 100% the aggregations? ... > Last but not the least: create a seperate cube for just the distinct ...
    (microsoft.public.sqlserver.olap)
  • Re: #ERR when trying to view detail of time dimension
    ... I erased the aggregations as a test only. ... > build your cube vs. MOLAP or HOLAP? ... I had put in a time dimension using the ... the new time dimension but with the different name works ...
    (microsoft.public.sqlserver.olap)