This hotfix also applies to Microsoft SQL Server 2014 Analysis Services (SSAS 2014).
Symptoms
Assume that a database corruption occurs in Microsoft SQL Server 2012 Analysis Services (SSAS 2012) or SQL Server 2014 Analysis Services (SSAS 2014). It may be difficult to determine which database is corrupted, and you cannot perform any administrator actions on the corrupted database. Additionally, you may receive an error message resembles the following:
Errors in the metadata manager. An error occurred when …. , from the file …..
For example, when you delete the source dimension of a linked dimension in SSAS 2012 or SSAS 2014, you receive an error message, and you cannot reprocess the linked dimension. This is the expected behavior, because the source dimension is deleted. However, after you restart the SSAS instance, you cannot delete or detach the issued database. Additionally, you cannot perform any administrator actions on the whole SSAS instance. Even though on unrelated databases, you cannot modify anything.After you apply this hotfix, the corrupted databases will get a "- SUSPECT" string appended to their name in Microsoft SQL Server Management Studio (SSMS). An administrator will be able to delete the suspect databases, as well as be able to perform any administrator actions on other normal databases. For the suspect databases, an administrator can obtain the actual corruption error by right-clicking on the databases and viewing their properties.Note This issue also occurs in SSAS 2008 and SSAS 2008 R2. The corresponding hotfixes will be released soon.
Resolution
The ability to isolate suspect corrupted database is released in the following cumulative update of SQL Server.
Cumulative Update 1 for SQL Server 2014 /en-us/help/2931693
Cumulative Update 8 for SQL Server 2012 SP1 /en-us/help/2917531
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
