MDS entity-based staging may fail when a duplicate Batch Tag value is used in SQL Server 2012
- You use the Microsoft SQL Server 2012 Master Data Services (MDS) entity-based staging process to import data into MDS.
- You populate various MDS staging tables (stg.name) with the staging data by using the BatchTag column to identify the batch.
- You use the same BatchTag value to populate a separate staging table that belongs to a different entity in a different MDS model.
- You run the necessary stored procedures to start the batch processing. Or, you start the staging batch from the Integration Management functional area on the MDS website.
When you start the staging process, you use one of three stored procedures:
Note The name placeholder is the name of the staging table that was specified when the entity was created.
The following examples show how to start the staging process by using the staging stored procedure:exec mds.stg.udp_entityname1 'versionAdescription',0,'batchtag'
exec mds.stg.udp_entityname2 'versionBdescription',0,'batchtag'
The status of the specified batch is not valid.
Additionally, when you check the batch status, you notice that the batch that has the BatchTag value remains indefinitely stuck in status Running.
Note You can check the batch status from the MDS website by clicking Integration Management and then selecting the model to view the status or by querying the [mdm].[tblStgBatch] table.
Article ID: 2712547 - Last Review: 11/19/2012 18:10:00 - Revision: 4.0
- kbtshoot kbexpertiseinter kbprb kbsurveynew KB2712547