FIX: PowerPivot database is not deleted from SSAS memory when PowerPivot database processing fails

Applies to: SQL Server 2008 R2 Service Pack 2SQL Server 2008 R2 PowerPivot for Excel 2010SQL Server 2012 Analysis Services

Symptoms


Assume that you have a PowerPivot database in Microsoft SQL Server 2008 R2 PowerPivot for Microsoft Excel 2010 or Microsoft SQL Server 2012 SP1 PowerPivot for Microsoft Excel 2010. Additionally, assume that PowerPivot database processing fails. In this situation, the following issues may occur:
  • The PowerPivot database may be left in the memory of Microsoft SQL Server Analysis Services (SSAS).
  • The memory usage of SSAS is high.
  • You can see more than one database that uses the name "sheetname" + "process" + "guid" in Microsoft SQL Server Management Studio (SSMS), the database directory and the backup directory.

Resolution


Cumulative update information

Cumulative update 8 for SQL Server 2012

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 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2844205 Cumulative update package 8 for SQL Server 2012
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 2012 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released

Cumulative Update 4 for SQL Server 2012 SP1

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to go to the article in the Microsoft Knowledge Base:
2833645 Cumulative update 4 for SQL Server 2012 SP1
Note Given that 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 SP1 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 go to the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Cumulative update 6 for SQL Server 2008 R2 Service Pack 2

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 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
2830140 Cumulative update package 6 for SQL Server 2008 R2 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 R2 Service Pack 2 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:
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

Status


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