Article ID: 2720619 - View products that this article applies to.
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.
Consider the following scenario:
This issue occurs because the relationship that has a dependency on the calculated column is selected arbitrarily. Therefore, the calculated column that depends on the relationship is processed before the relationship is processed.
Cumulative update information
SQL Server 2012The fix for this issue was first released in Cumulative Update 2. 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:
2703275Note 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:
(http://support.microsoft.com/kb/2703275/ )Cumulative update package 2 for SQL Server 2012
(http://support.microsoft.com/kb/2692828/ )The SQL Server 2012 builds that were released after SQL Server 2012 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around this issue, do not use the same name for the primary key column for each relationship.
Article ID: 2720619 - Last Review: November 19, 2012 - Revision: 2.0