Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


When you use Microsoft SQL Server 2012 or 2014 Master Data Services (MDS), the history can grow very big, and there is no built-in function to clean it up. Three stored procedures are added to clean up staging, validation, and transaction history. The usage is as follows:

--@ModelID is the model ID that you clean up the log for.
--@CLeanupOlderThanDate is the date before that the logs or records is deleted.

DECLARE @CleanupOlderThanDate date = '<Date>', @ModelID INT = <ID>
--Cleanup Transaction History
EXEC mdm.udpTransactionsCleanup @ModelID, @CleanupOlderThanDate;

--Cleanup Validation History
EXEC mdm.udpValidationsCleanup @ModelID, @CleanupOlderThanDate;

--Cleanup entity-based staging table
EXEC mdm.udpEntityStagingBatchTableCleanup @ModelID, @CleanupOlderThanDate;

Note The central tables that grow large are mdm.tblTransaction, mdm.tblTransactionAnnotation, mdm.tblValidationLog, mdm.tblValidationHistory, and mdm.tblStgBatch.

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:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!