Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
MDS entity-based staging may fail when a duplicate Batch Tag value is used in SQL Server 2012
Article ID: 2712547 - View products that this article applies to.
Consider the following scenario:
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.
This problem occurs because the MDS entity-based staging process checks the BatchTag status regardless of the MDS model.
If your batch is stuck in Running status, stop the batch process, and then try to process the batch again. To stop the batch process, run the following SQL statement:
Exec [mdm].[udpStagingBatchQueueActivate]To resolve this problem, update the BatchTag value in the staging table for the records to a new name. Additionally, make sure that the importstatus_ID field is set to 0 for the records.
For more information about starting the staging process, go to the following Microsoft Developer Network (MSDN) website:
Staging Stored Procedure (Master Data Services)Watch a video that shows how to use the new MDS entity-based staging in SQL Server 2012:
SQL 2012 Master Data Services - Entity Based StagingFor more information about how to populate the Master Data Services database, visit the following Microsoft TechNet website:
Importing Data (Master Data Services)For more information about the statuses when you import data during the staging process, visit the following Microsoft TechNet website:
Import Statuses (Master Data Services)