Microsoft distributes 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 2012 fix release.
This article describes a hotfix that reverts the ID for Analysis Management Objects (AMO) trace subclasses in SQL Server 2012 to earlier versions.
There is an enum that describes the subclass that you can use to do tracing in AMO. Each value in the enum can also be represented by an ID.
In SQL Server 2012, the values of these IDs are changed. For example, the trace subclass ID for the QueryBegin event was 45 in earlier versions of SQL Server. But in SQL Server 2012, the ID for that event is 62. After you apply the hotfix, the IDs are reverted to the values of earlier versions.
Cumulative update information
SQL Server 2012
The fix for this issue was first released in Cumulative Update 2 for SQL Server 2012 Service Pack RTM. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2703275 Cumulative update package 2 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. 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 Microsoft SQL Server 2012 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2012 Service Pack RTM hotfix to an installation of SQL Server 2012 Service Pack RTM. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
For more information about AMO Other Classes and Methods, go to the following Microsoft website:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.