dbTalk Databases Forums  

SSAS2005 - updating dimensions and length of

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


Discuss SSAS2005 - updating dimensions and length of in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Jesse O.
 
Posts: n/a

Default SSAS2005 - updating dimensions and length of - 05-09-2006 , 04:50 PM






We have several dimensions in our OLAP database.

For most of the dimensions, the updating time is realtively quick. However,
for others it's slow since it reprocesses all the underlying partitions.

Time is broken down like this:

--Processing Dimension "Time" completed successfully -duration 20 seconds
--Processing Cube "Sales" completed successfully --duration 2 seconds
--Processing Measure Goup "Sales measures" completed
uccessfully --duration 1 second


However other dimensions look like this:
--Processing Dimension "Business Unit" completed successfully -duration 7
seconds
--Processing Cube "Business Unit" completed successfully --duration 28
minutes
--Processing Measure Goup "Sales measures" completed
uccessfully --duration 27 minutes
--Processing Partition 'D_20060504' completed successfully.
<and so forth for every partition>


My question is...why do some dimensions require the processing of the
individual partitions while others do not? The processing of the other
dimensions is killing our load time.

This is something I need to understand asap since we're planning on rolling
it into production.


















Reply With Quote
  #2  
Old   
Akshai Mirchandani [MS]
 
Posts: n/a

Default Re: SSAS2005 - updating dimensions and length of - 05-09-2006 , 07:41 PM






Perhaps some dimensions have aggregations defined on them but others do not?
When a dimension is updated, aggregations/indexes may need to be rebuilt
depending on the changes to the dimension.

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=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.

"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote

Quote:
We have several dimensions in our OLAP database.

For most of the dimensions, the updating time is realtively quick.
However, for others it's slow since it reprocesses all the underlying
partitions.

Time is broken down like this:

--Processing Dimension "Time" completed successfully -duration 20
seconds
--Processing Cube "Sales" completed successfully --duration 2 seconds
--Processing Measure Goup "Sales measures" completed
ccessfully --duration 1 second


However other dimensions look like this:
--Processing Dimension "Business Unit" completed successfully -duration
7 seconds
--Processing Cube "Business Unit" completed successfully --duration 28
minutes
--Processing Measure Goup "Sales measures" completed
ccessfully --duration 27 minutes
--Processing Partition 'D_20060504' completed successfully.
and so forth for every partition


My question is...why do some dimensions require the processing of the
individual partitions while others do not? The processing of the other
dimensions is killing our load time.

This is something I need to understand asap since we're planning on
rolling it into production.




















Reply With Quote
  #3  
Old   
Jesse O.
 
Posts: n/a

Default Re: SSAS2005 - updating dimensions and length of - 05-09-2006 , 09:14 PM



That was my first thought, however that's not the case.

The only thing I can think of is the two dimensions that do require all the
partitions to be processed is that they are both part of a reference
dimension. Dimension "Business Unit" is a reference dimension of dimension
"Sales". Sales is not a reference dimension off of anything else.

Do reference dimensions or a dimension that is part of a reference dimension
required all the partitions to be processed after the dimension is updated?





"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote

Quote:
Perhaps some dimensions have aggregations defined on them but others do
not? When a dimension is updated, aggregations/indexes may need to be
rebuilt depending on the changes to the dimension.

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=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.

"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote in message
news:elcfdK7cGHA.564 (AT) TK2MSFTNGP02 (DOT) phx.gbl...
We have several dimensions in our OLAP database.

For most of the dimensions, the updating time is realtively quick.
However, for others it's slow since it reprocesses all the underlying
partitions.

Time is broken down like this:

--Processing Dimension "Time" completed successfully -duration 20
seconds
--Processing Cube "Sales" completed successfully --duration 2 seconds
--Processing Measure Goup "Sales measures" completed
cessfully --duration 1 second


However other dimensions look like this:
--Processing Dimension "Business Unit" completed successfully -duration
7 seconds
--Processing Cube "Business Unit" completed successfully --duration 28
minutes
--Processing Measure Goup "Sales measures" completed
cessfully --duration 27 minutes
--Processing Partition 'D_20060504' completed successfully.
and so forth for every partition


My question is...why do some dimensions require the processing of the
individual partitions while others do not? The processing of the other
dimensions is killing our load time.

This is something I need to understand asap since we're planning on
rolling it into production.






















Reply With Quote
  #4  
Old   
Akshai Mirchandani [MS]
 
Posts: n/a

Default Re: SSAS2005 - updating dimensions and length of - 05-10-2006 , 01:52 PM



I think if they are materialized (i.e. not Indirect), then yes. The
relationship between the referenced dimensions could have changed and so the
data in the partitions may not match anymore without re-processing.

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=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.

"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote

Quote:
That was my first thought, however that's not the case.

The only thing I can think of is the two dimensions that do require all
the partitions to be processed is that they are both part of a reference
dimension. Dimension "Business Unit" is a reference dimension of dimension
"Sales". Sales is not a reference dimension off of anything else.

Do reference dimensions or a dimension that is part of a reference
dimension required all the partitions to be processed after the dimension
is updated?





"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote in message
news:eIRYFq8cGHA.4148 (AT) TK2MSFTNGP05 (DOT) phx.gbl...
Perhaps some dimensions have aggregations defined on them but others do
not? When a dimension is updated, aggregations/indexes may need to be
rebuilt depending on the changes to the dimension.

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=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.

"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote in message
news:elcfdK7cGHA.564 (AT) TK2MSFTNGP02 (DOT) phx.gbl...
We have several dimensions in our OLAP database.

For most of the dimensions, the updating time is realtively quick.
However, for others it's slow since it reprocesses all the underlying
partitions.

Time is broken down like this:

--Processing Dimension "Time" completed successfully -duration 20
seconds
--Processing Cube "Sales" completed successfully --duration 2 seconds
--Processing Measure Goup "Sales measures" completed
essfully --duration 1 second


However other dimensions look like this:
--Processing Dimension "Business Unit" completed
ccessfully -duration 7 seconds
--Processing Cube "Business Unit" completed successfully --duration 28
minutes
--Processing Measure Goup "Sales measures" completed
essfully --duration 27 minutes
--Processing Partition 'D_20060504' completed successfully.
and so forth for every partition


My question is...why do some dimensions require the processing of the
individual partitions while others do not? The processing of the other
dimensions is killing our load time.

This is something I need to understand asap since we're planning on
rolling it into production.
























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.