Symptoms
Assume that you create a new Master Data Services (MDS) subscription view in Microsoft SQL Server 2012. The VersionMember_ID column does not exist in the subscription view that you have created.
This issue occurs because of a change in the SQL Server 2012 Master Data Services (MDS).
Resolution
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 1 for SQL Server 2012 /en-us/help/2679368
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:
More Information
When the subscription view is created in SQL Server 2012 MDS, the SQL Server view mdm.<subscription_view_name> no longer contains the VersionMember_ID column as it existed in SQL Server 2008 R2 MDS.
In Cumulative Update 1 for SQL Server 2012 SP1, an identity column was added back into subscription view. This new column contains the same data as the previous VersionMember_ID column. However, the new column is now named ID to make the column more explicit.
This hotfix can potentially break all custom data transfer jobs or scripts that are based on the SQL Server 2008 R2 MDS subscription view schema. Any jobs or scripts that reference the VersionMember_ID column have to be changed so that they reference the new ID column in the SQL Server 2012 MDS subscription views.
Additionally, in Cumulative Update 1 a new column MUID was added to subscription views to provide the member’s internal unique identifier value. The MUID column does not exist in SQL Server 2008 R2 MDS. You may have to update custom data transfer jobs in order to incorporate this new column.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about how to create a subscription view, go to the following MSDN website:
