Applies ToSQL Server 2012 Developer SQL Server 2012 Enterprise SQL Server 2012 Standard SQL Server 2014 Business Intelligence - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use)

Symptoms

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 HistoryEXEC mdm.udpTransactionsCleanup @ModelID, @CleanupOlderThanDate;--Cleanup Validation HistoryEXEC mdm.udpValidationsCleanup @ModelID, @CleanupOlderThanDate;--Cleanup entity-based staging tableEXEC 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:

Status

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.