Article ID: 2803065 - View products that this article applies to.
Consider the following scenario:
Cumulative update information
Cumulative Update 3 for SQL Server 2012 Service Pack 1 (SP1)The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012 SP 1, click the following article number to view the article in the Microsoft Knowledge Base:
2812412Note 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 SP 1 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:
(http://support.microsoft.com/kb/2812412/ )Cumulative update package 3 for SQL Server 2012 Service Pack 1
(http://support.microsoft.com/kb/2772858/ )The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The following table provides more information about the products or tools that automatically check for the condition that is described in the "Symptoms" section in your instance of SQL Server and in the versions of SQL Server against which the rule is evaluated:
Collapse this tableExpand this table
Article ID: 2803065 - Last Review: January 30, 2014 - Revision: 2.0