![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, again with some aggregation questions... I try to opimize my partitions. in a cube I have some measure groups based on tables from 1.5 million of rows to 150millions. to opimize my bigest partitions, I have set the aggregationusage to FULL for the attributes in 3 main dimensions. This reduce the cold cache access from 33seconds to 5seconds. good but this optimization cause my 1.5million of rows partition to be evaluated with 0 aggregation! this measure group use a dimension which disallow aggregation (like a budget or version dimension where the All member mean nothing) But I found this result strange, why SSAS create no aggregation for this partition? The biggest measure group use the same dimensions accept the non-aggregated one. So I don't understand what's appends. any guide? Jerome. |
#3
| |||
| |||
|
|
What are the aggregation functions you are using in the two cubes? Marco Russo http://www.sqlbi.eu http://www.sqljunkies.com/weblog/sqlbi Jeje wrote: Hi, again with some aggregation questions... I try to opimize my partitions. in a cube I have some measure groups based on tables from 1.5 million of rows to 150millions. to opimize my bigest partitions, I have set the aggregationusage to FULL for the attributes in 3 main dimensions. This reduce the cold cache access from 33seconds to 5seconds. good but this optimization cause my 1.5million of rows partition to be evaluated with 0 aggregation! this measure group use a dimension which disallow aggregation (like a budget or version dimension where the All member mean nothing) But I found this result strange, why SSAS create no aggregation for this partition? The biggest measure group use the same dimensions accept the non-aggregated one. So I don't understand what's appends. any guide? Jerome. |
#4
| |||
| |||
|
|
aggregation function??? I'm not sure if I understand the question. All my measure group/partitions are MOLAP based in my case everything is in the same cube to simplify I have 2 measure groups, to optimize my cube, I have 3 main attributes (1 in each main dimension) where the aggregationusage is set to full. These dimensions are used in the 2 measure group I have another dimension where the Isaggregate option is set to false (so there is no "All member" for this dimension) This non aggregatable dimension is associated to the 1.5 millions rows. The result of this combination of options result in 0 aggregation designed for the 1.5 millions rows measure group. While the big measure group is correctly optimized. If I change the aggregationusage from full to default, then all the partitions are evaluated with aggregations, but the performance is bad for my big partitions. I hope I'm clear in my description :-) "Marco Russo" <marco.russo (AT) loader (DOT) it> wrote in message news:1165360019.223351.191780 (AT) l12g2000cwl (DOT) googlegroups.com... What are the aggregation functions you are using in the two cubes? Marco Russo http://www.sqlbi.eu http://www.sqljunkies.com/weblog/sqlbi Jeje wrote: Hi, again with some aggregation questions... I try to opimize my partitions. in a cube I have some measure groups based on tables from 1.5 million of rows to 150millions. to opimize my bigest partitions, I have set the aggregationusage to FULL for the attributes in 3 main dimensions. This reduce the cold cache access from 33seconds to 5seconds. good but this optimization cause my 1.5million of rows partition to be evaluated with 0 aggregation! this measure group use a dimension which disallow aggregation (like a budget or version dimension where the All member mean nothing) But I found this result strange, why SSAS create no aggregation for this partition? The biggest measure group use the same dimensions accept the non-aggregated one. So I don't understand what's appends. any guide? Jerome. |
#5
| |||
| |||
|
|
Sorry, I mean what is the "AggregateFunction" property of the involved measures. By default it is Sum, but you can have others (Min, Max, DistinctCount, ByAccount, LastChild, ...). If you have the default Sum, I would suggest you to open a case with Microsoft with a specific sample of the problem (or use http://connect.microsoft.com), it is hard to understand what's happening without the real data. Marco Russo http://www.sqlbi.eu http://www.sqljunkies.com/weblog/sqlbi Jeje wrote: aggregation function??? I'm not sure if I understand the question. All my measure group/partitions are MOLAP based in my case everything is in the same cube to simplify I have 2 measure groups, to optimize my cube, I have 3 main attributes (1 in each main dimension) where the aggregationusage is set to full. These dimensions are used in the 2 measure group I have another dimension where the Isaggregate option is set to false (so there is no "All member" for this dimension) This non aggregatable dimension is associated to the 1.5 millions rows. The result of this combination of options result in 0 aggregation designed for the 1.5 millions rows measure group. While the big measure group is correctly optimized. If I change the aggregationusage from full to default, then all the partitions are evaluated with aggregations, but the performance is bad for my big partitions. I hope I'm clear in my description :-) "Marco Russo" <marco.russo (AT) loader (DOT) it> wrote in message news:1165360019.223351.191780 (AT) l12g2000cwl (DOT) googlegroups.com... What are the aggregation functions you are using in the two cubes? Marco Russo http://www.sqlbi.eu http://www.sqljunkies.com/weblog/sqlbi Jeje wrote: Hi, again with some aggregation questions... I try to opimize my partitions. in a cube I have some measure groups based on tables from 1.5 million of rows to 150millions. to opimize my bigest partitions, I have set the aggregationusage to FULL for the attributes in 3 main dimensions. This reduce the cold cache access from 33seconds to 5seconds. good but this optimization cause my 1.5million of rows partition to be evaluated with 0 aggregation! this measure group use a dimension which disallow aggregation (like a budget or version dimension where the All member mean nothing) But I found this result strange, why SSAS create no aggregation for this partition? The biggest measure group use the same dimensions accept the non-aggregated one. So I don't understand what's appends. any guide? Jerome. |
#6
| |||
| |||
|
|
its sum and/or count aggregations in each measure group. but the same aggregations are designed for my DCount measures (which are in dedicated measure group) "Marco Russo" <marco.russo (AT) loader (DOT) it> wrote in message news:1165394522.747223.190920 (AT) n67g2000cwd (DOT) googlegroups.com... Sorry, I mean what is the "AggregateFunction" property of the involved measures. By default it is Sum, but you can have others (Min, Max, DistinctCount, ByAccount, LastChild, ...). If you have the default Sum, I would suggest you to open a case with Microsoft with a specific sample of the problem (or use http://connect.microsoft.com), it is hard to understand what's happening without the real data. Marco Russo http://www.sqlbi.eu http://www.sqljunkies.com/weblog/sqlbi Jeje wrote: aggregation function??? I'm not sure if I understand the question. All my measure group/partitions are MOLAP based in my case everything is in the same cube to simplify I have 2 measure groups, to optimize my cube, I have 3 main attributes (1 in each main dimension) where the aggregationusage is set to full. These dimensions are used in the 2 measure group I have another dimension where the Isaggregate option is set to false (so there is no "All member" for this dimension) This non aggregatable dimension is associated to the 1.5 millions rows. The result of this combination of options result in 0 aggregation designed for the 1.5 millions rows measure group. While the big measure group is correctly optimized. If I change the aggregationusage from full to default, then all the partitions are evaluated with aggregations, but the performance is bad for my big partitions. I hope I'm clear in my description :-) "Marco Russo" <marco.russo (AT) loader (DOT) it> wrote in message news:1165360019.223351.191780 (AT) l12g2000cwl (DOT) googlegroups.com... What are the aggregation functions you are using in the two cubes? Marco Russo http://www.sqlbi.eu http://www.sqljunkies.com/weblog/sqlbi Jeje wrote: Hi, again with some aggregation questions... I try to opimize my partitions. in a cube I have some measure groups based on tables from 1.5 million of rows to 150millions. to opimize my bigest partitions, I have set the aggregationusage to FULL for the attributes in 3 main dimensions. This reduce the cold cache access from 33seconds to 5seconds. good but this optimization cause my 1.5million of rows partition to be evaluated with 0 aggregation! this measure group use a dimension which disallow aggregation (likea budget or version dimension where the All member mean nothing) But I found this result strange, why SSAS create no aggregation for this partition? The biggest measure group use the same dimensions accept the non-aggregated one. So I don't understand what's appends. any guide? Jerome. |
#7
| |||
| |||
|
#8
| |||
| |||
|
|
I'm guessing that no aggregations get designed for the measure group with the "dimension where the Isaggregate option is set to false" because, with the 3 main attributes automatically included by Full AggreationUsage, the aggregations would be too large So, what if you set Aggregation Usage for the "3 main attributes (1 in each main dimension)" to Unrestricted, rather than Full? - Deepak Deepak Puri Microsoft MVP - SQL Server *** Sent via Developersdex http://www.developersdex.com *** |
#9
| |||
| |||
|
|
using the unrestricted option don't create good aggregations and my cube is too slow "Deepak Puri" <deepak_puri (AT) progressive (DOT) com> wrote in message news:uEI$N6$GHHA.4904 (AT) TK2MSFTNGP04 (DOT) phx.gbl... I'm guessing that no aggregations get designed for the measure group with the "dimension where the Isaggregate option is set to false" because, with the 3 main attributes automatically included by Full AggreationUsage, the aggregations would be too large So, what if you set Aggregation Usage for the "3 main attributes (1 in each main dimension)" to Unrestricted, rather than Full? - Deepak Deepak Puri Microsoft MVP - SQL Server *** Sent via Developersdex http://www.developersdex.com *** |
![]() |
| Thread Tools | |
| Display Modes | |
| |