Microsoft distributes Microsoft SQL Server 2008 SP2 or Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 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 SP2 or SQL Server 2008 R2 or Microsoft SQL Server 2012 fix release.
Symptoms
Consider the following scenario:
-
You run a ProcessUpdate command against a cube in Microsoft SQL Server 2008 Analysis Services (SSAS 2008) or in Microsoft SQL Server 2008 R2 Analysis Services (SSAS 2008 R2).
-
The cube has partitions that use aggregation designs.
In this scenario, you receive an error message that resembles the following:
The file 'file name' could not be opened. Please check the file for permissions or see if other applications locked it.The file 'file name' could not be deleted. Please check the file for permissions.
Notes
-
This error message can be found in the Application log and in the Msmdsrv.log file, but cannot be found in SQL profiler trace.
-
The error only occurs on files that have the agg.flex.map or agg.flex.map.hdr file name extensions.
Cause
This issue occurs because of problems with the flexible aggregation indexes when the ProcessUpdate command is running.
Resolution
Cumulative update information
SQL Server 2008 R2 Service Pack 1
The fix for this issue was first released in Cumulative Update 6 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:
2679367 Cumulative Update package 6 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
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 12. 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:
2659692 Cumulative Update package 12 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 Service Pack 3
The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2648098 Cumulative update package 3 for SQL Server 2008 Service Pack 3Note 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:
2629969 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. 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 (SP2) cumulative update package 7
Before you apply this hotfix, SSAS 2008 builds bitmap indexes (.map files) for both the partition fact data (.fact.data files) and the aggregation data (.agg.flex.data and .agg.rigid.data files). After you apply this hotfix, bitmap indexes for the aggregation data are not created, but bitmap indexes continue to be built for the fact data files.The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
2617148 Cumulative update package 7 for SQL Server 2008 Service Pack 2Note 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 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:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Workaround
To work around this issue, use one of the following methods:
-
Do not use aggregation designs in partitions.
-
Run the ProcessUpdate command again if there are no other queries to execute.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
