none
Altering aggregations, overrides previous created aggregations

    Question

  • When an alter command is initiated as a SOAP request on SSAS, altering previously created  aggregation design, this alter command overrides the previously created aggregations and inserts new aggregations into the aggregation design.

    The SOAP request is initiated via JAVA application.

    What alteration command should be fired so that previously created aggregations are not overriden.

    The following is the alter command:

    <?xml version="1.0" encoding="UTF-8"?>
    <Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/">
        <Header>
            <BeginSession xmlns="urn:schemas-microsoft-com:xml-analysis"/>
            </Header>
            <Body>
                <Execute xmlns="urn:schemas-microsoft-com:xml-analysis">
                    <Command>


    <Alter ObjectExpansion="ObjectProperties" xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
    <Object>
    <DatabaseID>DATABASE_ID</DatabaseID>
    <CubeID>CUBE_ID</CubeID>
    <MeasureGroupID>MEASURE_GROUP_ID</MeasureGroupID>
    <AggregationDesignID>DESIGN_ID</AggregationDesignID><!--Previously created aggregations design-->
    </Object>
    <ObjectDefinition>
    <AggregationDesign xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlns:ddl100_100="http://schemas.microsoft.com/analysisservices/2008/engine/100/100" xmlns:ddl200="http://schemas.microsoft.com/analysisservices/2010/engine/200" xmlns:ddl200_200="http://schemas.microsoft.com/analysisservices/2010/engine/200/200" xmlns:ddl300="http://schemas.microsoft.com/analysisservices/2011/engine/300" xmlns:ddl300_300="http://schemas.microsoft.com/analysisservices/2011/engine/300/300" xmlns:ddl400="http://schemas.microsoft.com/analysisservices/2012/engine/400" xmlns:ddl400_400="http://schemas.microsoft.com/analysisservices/2012/engine/400/400">
    <ID>DESIGN_ID</ID>
    <Name>DESIGN_ID</Name>
    <EstimatedRows>648529</EstimatedRows>

    <Aggregations>

    <Aggregation><!--Aggregation1 that should be added--></Aggregation>

    <Aggregation><!--Aggregation2 that should be added--></Aggregation>

    </Aggregations>

    </AggregationDesign>
    </ObjectDefinition>
    </Alter>
    </Command>
     <Properties>
                        <PropertyList>
                            <DataSourceInfo>192.168.2.69</DataSourceInfo>
                            <Format>Multidimensional</Format>
                            <Catalog>CATLOG_NAME</Catalog>
                        </PropertyList>
                    </Properties>
    </Execute>
    </Body>
    </Envelope>

    DESIGN_ID: Is already created aggregation using SSAS. Previously created aggregation design has around 10 aggregations, altering this aggregation design to add above two aggregation.

    But, this two aggregations overrides previously created 10 aggregations

    Wednesday, May 23, 2018 3:23 PM

All replies

  • Hi sridar1992,

    Thanks for your question.

    Just like you said in another post , "A single partition can have only one aggregation assigned to it, and only one partition is required by the design." I do not know why do you want to assign multiple aggregations to a single partition, since it can only apply one.

    See below similar thread assign an aggregation design to a singe partition:
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/7d918d98-7f37-495f-a2dc-5a003bc1c8a2/xmla-script-assign-aggregation-design?forum=sqlanalysisservices


    Best Regards
    Willson Yuan
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, May 24, 2018 1:50 AM
    Moderator
  • Yes, but we need default and custom aggregations to be merged in a single AggregationDesign
    Friday, June 01, 2018 8:14 AM
  • Hi sridar1992,

    Thanks for your response.

    >>>Yes, but we need default and custom aggregations to be merged in a single AggregationDesign

    In this scenario, please go to cube design--Aggregations, click on advance view, then you can custom the default aggregation, see below screenshot:


    Best Regards
    Willson Yuan
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    • Proposed as answer by alexander fun Friday, June 08, 2018 11:24 AM
    Friday, June 01, 2018 8:47 AM
    Moderator
  • Thanks for your kind reply!

    But, how one can achieve the same thing using XMLA.

    Thank you in advance!

    Monday, June 04, 2018 9:16 AM
  • Anyone with some light on this issue would be helpful.

    Thank you!

    Tuesday, June 05, 2018 7:30 AM
  • Hi sridar1992,

    Thanks for your response.

    >>>Anyone with some light on this issue would be helpful.

    Since we can achieve this through GUI directly, you can just set it in there.  It is not necessary to do it using XMLA. To be honest, I can not find any documents about to achieve this using XMLA.


    Best Regards
    Willson Yuan
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, June 08, 2018 2:40 AM
    Moderator
  • I got the issue resolved, as XMLA in SSAS works as 0/1, either it creates or replaces.

    If, one wants to add something extra in existing aggregation design, one must have its previous XMLA-Make changes in it-then execute it.

    Hope it would be helpful for someone with the same issue.

    Thank you!

    Thursday, June 14, 2018 6:53 AM
  • Hi sridar1992,

    Thanks for sharing the solution. I am glad to know that you have found the solution by yourself, Please kindly mark it as an answer to close this thread.


    Best Regards
    Willson Yuan
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, June 14, 2018 8:01 AM
    Moderator