This blog provides information, news, tips, and announcements about the SQL Server Data Quality Services (DQS) feature introduced in SQL Server 2012.
After you’ve downloaded Denali CTP3, it’s time to install DQS!
Here you can find some important information that will help you install and configure DQS successfully.
Data Quality Services (DQS) contains three components: DQS server, DQS client, and a DQS Cleansing SSIS component. The DQS server is installed on top of the SQL Server Database Engine, and includes two databases: DQS_MAIN and DQS_PROJECTS. DQS_MAIN db contains all the DQS stored procedures, its engine and the published knowledge bases. The DQS_PROJECTS db contains all the data quality projects information. The DQS client is a standalone application that enables you to connect to a DQS server, providing you with a highly-intuitive graphical user interface to perform your data-cleansing tasks, as well as other administrative tasks related to DQS. The DQS Cleansing SSIS component enables you to integrate the DQS functionality into an SSIS data flow, for batch execution. Each of these 3 components can be installed on separate machines, or on the same one – according to your needs. Refer to the DQS Help documentation for additional details on DQS and how it can be used.
All DQS components are installed through the SQL Server Denali Setup. Watch this video to walk through the DQS installation and configuration, step by step. For more detailed information, refer to the DQS Installation Guide.
Please pay attention: in order to complete the DQS server installation, some post-installation steps must be performed. Otherwise, DQS server will not be functional. These steps are explained in the resources mentioned above.
Do you experience any issues during installation? Check this page for troubleshooting, refer to CTP3 release notes, or contact us.
The DQS Team
When execute DQSInstaller.exe, the log for error is below:
Msg 10314, Level 16, State 11, Server USER-PC\MARTIN, Line 1
[7/30/2011 11:51:40 AM] An error occurred in the Microsoft .NET Framework while trying to load assembly id 65572. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:
[7/30/2011 11:51:40 AM] System.IO.FileLoadException: Could not load file or assembly 'microsoft.ssdqs.core, Version=188.8.131.52, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. Assembly in host store has a different signature than assembly in GAC. (Exception from HRESULT: 0x80131050) See Microsoft Knowledge Base article 949080 for more information.
[7/30/2011 11:51:40 AM] System.IO.FileLoadException:
[7/30/2011 11:51:40 AM] at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
[7/30/2011 11:51:40 AM] at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection, Boolean suppressSecurityChecks)
[7/30/2011 11:51:40 AM] at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
[7/30/2011 11:51:40 AM] at System.Reflection.Assembly.Load(String assemblyString)
How can I resolve the issue?
The simple solution is to install Denali CTP3 on a clean machine (with no previous DQS installation).
We're investigating the problem and we'll update you soon with a workaround, in case you can't install on a clean machine.
The problem is caused by an inappropriate handling of DQS assemblies installed in the GAC from previous version.
If you would like to prevent the need to use a clean machine, a possible solution is to uninstall the DQS and SSIS features of your current installation (this will remove the old assemblies), and then install Denali CTP3.
The problem is caused by inappropriate handling of DQS assemblies installed in the GAC from previous version.
If you would like to prevent the need to use a clean machine, a possible solution is to uninstall the DQS and SSIS features from your current installation (this will remove the old assemblies), and then install Denali CTP3.
I attempted to install DQS on a clean machine. I recieved the error mention above. Is there a way to add the Trust to the stored procedure or switch the database owner to 'sa'? It seems like this has to be done during the installation and before that script runs.
Here is the solution to the problem...
The Hotfix that is distributed with the CTP3 breaks DQS... Uninstall it and it works fine.
Data Quality Client isn't shown in All Programs->Microsoft SQL Server 2012 RC0->Data Quality Services menu after runing DQSInstaller.exe from Command Prompt. I upgrade SQL from CTP3 to RC0(DQS feature is added after upgrade to RC0). so there are two folders under C:\Program Files\Microsoft SQL Server, one is MSSQL11.MSSQLSERVER, the other is MSSQL11.MSSQLSERVER1750 where DQSInstaller.exe is located, but it failed to execute under the folder since it try to connect to MSSQLSERVER1750 instance. I copy DQSInstaller.exe to MSSQL11.MSSQLSERVER\MSSQL\Binn, and execute it successfully.
Here is the log:
[1/16/2012 6:44:03 PM] Setting the collation to default value: SQL_Latin1_General_CP1_CI_AS
[1/16/2012 6:44:04 PM] Using instance: MSSQLSERVER, catalog: DQS.
[1/16/2012 6:44:04 PM] Executing action: Validate collation argument
[1/16/2012 6:45:39 PM] * Register .NET dependency assemblies
[1/16/2012 6:45:59 PM] Warning: The Microsoft .NET Framework assembly 'system.management, version=184.108.40.206, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[1/16/2012 6:45:59 PM] Warning: The Microsoft .NET Framework assembly 'system.configuration.install, version=220.127.116.11, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details
[1/16/2012 6:46:58 PM] Started loading knowledgebase 'DQS Data'
[1/16/2012 6:51:31 PM] Finished loading knowledgebase 'DQS Data'
[1/16/2012 6:51:31 PM] Action 'Load out of the box data' finished successfully.
[1/16/2012 6:51:31 PM] DQS Installer finished successfully.
How to resolve it?