Article ID: 2422081 - Last Review: February 21, 2011 - Revision: 4.0

FIX: The memory usage in SSAS 2008 or SSAS 2008 R2 may be larger than in SSAS 2005 when you create a local cube

Hotfix download is availableHotfix Download Available
View and request hotfix downloads
View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Microsoft distributes Microsoft SQL Server 2008 or 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 or 2008 R2 fix release.

On This Page

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • You have Microsoft SQL Server 2008 Analysis Services (SSAS 2008) or Microsoft SQL Server 2008 R2 Analysis Services (SSAS 2008 R2)installed on a computer.
  • You create a local cube from a server-based cube.
In this scenario, the memory usage of the local cube may be large compared to the memory usage of the local cube in Microsoft SQL Server 2005 Analysis Services (SSAS 2005).
Back to the top

CAUSE

This issue occurs because SSAS 2008 or SSAS 2008 R2 caches all Multidimensional Expressions (MDX) subcube statements in memory. Therefore, the memory usage is high when you run the MDX query to create the local cube file.
Back to the top

RESOLUTION

Cumulative update information

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 6. 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:
2489376  (http://support.microsoft.com/kb/2489376/ ) Cumulative Update package 6 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  (http://support.microsoft.com/kb/981356/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008

The fix for this issue was first released in Cumulative Update 11 for SQL Server 2008 Service Pack 1.

For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2413738  (http://support.microsoft.com/kb/2413738/LN/ ) Cumulative update package 11 for SQL Server 2008 Service Pack 1
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 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:
970365  (http://support.microsoft.com/kb/970365/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2467239  (http://support.microsoft.com/kb/2467239/LN/ ) Cumulative update package 2 for SQL Server 2008 Service Pack 2
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 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:
2402659  (http://support.microsoft.com/kb/2402659/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Back to the top

STATUS

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

WORKAROUND

To work around this issue, following these steps:
  1. Set the following SQL Server property in the Msmdsrv.ini file.
    <DisableCalcExpressNonEmpty>1</DisableCalcExpressNonEmpty>

  2. Store the Config file, and then restart SSAS 2008 or SSAS 2008 R2.
Note The Config file is located in the following directory:
\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
Back to the top

REFERENCES

For more information about how to create a GLOBAL CUBE statement that has MDX statements, visit the following Microsoft Developer Network (MSDN) website:
How to create a GLOBAL CUBE statement that has MDX statements (http://msdn.microsoft.com/en-us/library/ms145581(v=SQL.100).aspx)
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897  (http://support.microsoft.com/kb/935897/ ) An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499  (http://support.microsoft.com/kb/822499/ ) New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
APPLIES TO
  • Microsoft SQL Server 2008 Analysis Services
  • Microsoft SQL Server 2008 R2 Analysis Services
Back to the top
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix KB2422081
Back to the top