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:
You use Master Data Services Entity-Based Staging (EBS) to change the value of an attribute for an entity in Microsoft SQL Server 2012. The original value of the attribute is NULL.
You run a staging process stored procedure to execute the staging process, and you set the value of the LogFlag parameter to 1.
Note When the value of the LogFlag parameter is set to 1, transactions are logged after the staging process starts.
In this scenario, the transaction history does not log the changes.
This issue does not occur when you use the Master Data Services Web application instead of the stored procedure to execute the staging process.
This issue only occurs if the original value of the attribute is NULL.
Cumulative update information
SQL Server 2012
The 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:
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 has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.