Article ID: 2685743 - View products that this article applies to.
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 perform the Discovery activity or the Cleansing activity in SQL Server 2012 Data Quality Services (DQS), the DQS_PROJECTS database may grow very quickly. The transient X_ tables in the DQS_PROJECT database especially quickly.
In particular, you may experience the following issues for the Discovery activity:
This issue occurs for one or more of the following reasons:
Cumulative update information
SQL Server 2012The fix for this issue was first released in Cumulative Update 2 for SQL Server 2012 Service Pack RTM. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2703275Note 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 2012 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:
(http://support.microsoft.com/kb/2703275/LN/ )Cumulative update package 2 for SQL Server 2012
2692828Microsoft SQL Server 2012 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2012 Service Pack RTM hotfix to an installation of SQL Server 2012 Service Pack RTM. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/2692828/LN/ )The SQL Server 2012 builds that were released after SQL Server 2012 was released
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, delete unnecessary data projects and knowledge bases in DQS to help minimize the footprint of the internal tables that are used by the projects.
After you apply this fix, the DQS_PROJECT database size will not automatically decrease. For more information about how to reduce the size of a database, go to the following Microsoft website:
How to shrink a databaseNote Installing this hotfix alone does not correct the database growth problems that have occurred in the past, and only is helpful for new projects and activities which are created in the future, and projects and activities which are finished in the future.
To manually reduce the size of DQS databases, review the knowledge bases that are no longer used or the data quality projects that are already finished.
You can use the data quality client, and then click Open Knowledge Base or Open Data Quality Project to obtain the list of each knowledge base or each project. Right-click the knowledge base name or project name, and then click Delete.
You can run the following Transact-SQL script to help estimate the size of each knowledge base and each project that is located in the DQS_MAIN and DQS_PROJECTS databases to better gauge the disk space that is consumed by each.
After you install this hotfix, when DQS creates the internal table X_INDEX_DATA_SOURCE_TABLE within each project's schema, the SPARSE hint is used on the BigInt columns to minimize the space that is used by empty rows and columns to minimize the disk space that is required to hold those objects. This hotfix lets DQS release the transient X_INDEX_DATA_SOURCE_TABLE object. Therefore, the space may be reused, or the size of the database can be reduced after the knowledge base is published or the data quality project is finished. Therefore, when you click the Finish button at the end of the projects, you help free the disk space that is consumed by the activity.