Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
When you use Data Quality Services (DQS) to perform a data cleansing against a large data source in Microsoft SQL Server 2012, slow performance occurs in SQL Server 2012. For example, it may take longer than 18 hours to complete the data cleansing against a data source that has 1.5 million records. When this issue occurs, you may also receive one or more of the following error messages:
Error message 1
Flow ended with an application error.
Microsoft.Ssdqs.Core.Context.ResponseException: Correction flow fatal error. ---> System.Data.SqlClient.SqlException: Transaction (Process ID 41) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Error message 2
Flow ended with an application error.
Microsoft.Ssdqs.Core.Context.ResponseException: Failed to execute calibrator, or an error occurred during calibration. ---> System.Data.SqlClient.SqlException: Insert bulk failed due to a schema change of the target table.
This issue occurs because the internal processing for millions of source rows happens in small chunks during DQS data cleansing. However, each transaction runs across parallel threads. When the data source is large, and there are many transactions that run across parallel threads, deadlock occurs. Therefore, the issue that is described in the "Symptoms" section occurs.
Cumulative update information
SQL Server 2012
The fix for this issue was first released in Cumulative Update 1 for SQL Server 20012. For more information about how to obtain this cumulative update package for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
2679368 Cumulative update 1 for SQL Server 2012Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was releasedAfter you install this cumulative update, you have to run the DQSInstaller.exe file to upgrade the DQS schema. To run the DQSInstaller.exe file, follow these steps:
Run the following command to locate to the instance folder:
cd "C:\Program Files\Microsoft SQL Server\MSSQL11.<InstanceName>\MSSQL\Binn"
Run the following command to upgrade the DQS schema:
Note We recommend that you back up the DQS_MAIN and DQS_PROJECTS databases before you install this cumulative update.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around this issue, perform the data cleansing on a small set of source data at a time.
For more information about how to upgrade DQS, visit the following Microsoft website:
How to upgrade DQSFor more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problemsFor more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 Naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates