Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

Consider the following scenario:

  • You create a Multidimensional Expressions (MDX) query in Microsoft SQL Server 2008 R2 Analysis Services (SSAS 2008 R2) or in Microsoft SQL Server 2012 Analysis Services (SSAS 2012).

  • The query uses unary operators on some members in a parent/child hierarchy.

  • You define a scope calculation on these members in the parent/child hierarchy.

  • The query accesses multiple dates in a time dimension

  • You run the query.


In this scenario, the query performs slowly. Additionally, you may receive the following error message:

Executing the query ...
XML for Analysis parser: The XML for Analysis request timed out before it was completed.

Note This issue does not occur if you run the same query in Microsoft SQL Server 2000 Analysis Services (SSAS 2000).

Resolution

To resolve this issue, apply the following hotfix. After you install the hotfix, a new property (CellByCellCalculationMode) is available for you to configure in the Analysis Services configuration file (Msmdsrv.ini). To resolve this performance issue, add this property and change the default value of CellByCellCalculationMode from 0 to 3. After you do this, the Msmdsrv.ini file should contain the following node under the <Query> section:

<CellByCellCalculationMode>3</CellByCellCalculationMode>


Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2679368 Cumulative update package 1 for SQL Server 2012Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:

2534352 Cumulative Update package 8 for SQL Server 2008 R2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 R2 Service Pack 1



The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2633146 Cumulative Update package 4 for SQL Server 2008 R2 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about unary operators, visit the following MSDN website:

General information about unary operators

For more information about the SCOPE statement, visit the following MSDN website:

General information about the SCOPE statement

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×