Data Quality Services MSDN Forum.

If you want to contribute to this article, use the Edit tab at the top (require sign-in). This article will be updated as and when we come across new issues, or resolve existing issues.

While installing/configuring DQS, you might encounter any of the following issues:

• Cannot find the DQSInstaller.exe file or the Data Quality Server Installer option in the Start menu
• When multiple instances are installed, the Start menu item for running DQSInstaller works only for the latest instance
• Error on reinstalling Data Quality Server  
• Error: Could not find stored procedure 'SP_PROCOPTION'. Dqs could not be installed
• Warning: The Microsoft .NET Framework assembly you are registering is not fully tested in SQL Server hosted environment.
• Error when special character or accented character appears in TMP environment variable folder
• Error: Cannot write into file 'dqs_certificate.cer' 

---

Cannot find the DQSInstaller.exe file or the Data Quality Server Installer option in the Start Menu 

The Data Quality Server Installer option in the Start menu or the DQSInstaller.exe file is available at C:\Program Files\Microsoft SQL Server\MSSQL11.<instance_name>\MSSQL\Binn only if you selected the Data Quality Services check box under Database Engine Services on the Feature Selection page while installing SQL Server 2012.

To fix the issue, run the SQL Server setup again, and add the DQS server to the existing SQL Server instance by selecting the Data Quality Services check box on the Feature Selection page. For more information about adding a feature to an existing SQL Server instance, see Add Features to an Instance of SQL Server 2012 (Setup).


Return to Top

---

When multiple instances are installed, the Start menu item for running DQSInstaller works only for the latest instance

The item to run DQSInstaller in the Start menu (Data Quality Services > Data Quality Server Installer) points to the last instance of DQS installed when multiple instances of SQL Server Engine and Data Quality Services are installed in sequence. Since DQS is installed per instance, you must run the DQSInstaller once for each instance separately if you wish to use DQS with each instance.

The workaround is to:

1. Launch the command prompt window as an administrator.
2. Change directory to the program files folder for the instance of DQS which you want to install. For example:
   cd "C:\Program Files\Microsoft SQL Server\MSSQL11.<InstanceName>\MSSQL\Binn\"
3. Run the DQSInstaller.exe to completion.

For more switches see also Run DQSInstaller.exe to Complete Data Quality Server Installation.

Return to Top

---

 

Error on reinstalling Data Quality Server

When you run the DQSInstaller.exe file to reis to:

1. Launch the command prompt window as an administrator.
2. Change directory to the program files folder for the instance of DQS which you wantnstall Data Quality Server on a SQL Server instance on a computer where it was previously installed, you might receive the following error:

   “Cannot create file ‘C:\Program Files\Microsoft SQL Server\MSSQL11.\MSSQL\DATA\DQS_MAIN.mdf' because it already exists.”

   This occurs because DQS databases (DQS_MAIN and DQS_PROJECTS) from the previous DQS server installation are still present on your computer even after you uninstalled DQS server. When you uninstall DQS server or a SQL Server instance containing DQS server, some DQS objects are not removed from the computer. You must manually delete those DQS objects after uninstalling DQS server or a SQL Server instance containing DQS server. To fix this issue:

   1. Exit the currently active DQS server installation by closing the DQSInstaller.exe window.
   2. Manually delete the existing DQS objects from previous installation. For more information about removing DQS objects, see Remove Data Quality Services Objects.
   3. Run the DQSInstaller.exe file to reinstall DQS. For more information, see Run DQSInstaller.exe to Complete Data Quality Server Installation.
   Return to Top

   ---

   Error: Could not find stored procedure 'SP_PROCOPTION'. Dqs could not be installed

   When you run the DQSInstaller.exe file to complete the DQS server installation, you might receive the following error:

   “Could not find stored procedure 'SP_PROCOPTION'. Dqs could not be installed.”

   This occurs because some accent-sensitive server collation (for example, Turkish_CI_AS) is set on the SQL Server instance where you are installing Data Quality Server, and DQS does not support it. If you require accent-sensitive server collation for your SQL Server instance, you must install Data Quality Server in another SQL Server instance that has accent-insensitive server collation. For more information about collations in SQL Server, see Working with Collations.

   Return to Top

   ---

   Warning: The Microsoft .NET Framework assembly you are registering is not fully tested in SQL Server hosted environment.

   When you run the DQSInstaller.exe to complete the DQS server installation, you will receive the following warnings in the console output and in the DQSInstaller.log
   
   DQS has dependencies on system assemblies, like System.Web. Any references to outside assemblies are considered Unsafe in SQL CLR, so it prints the warning for each one that DQS registers. DQS uses SQL CLR procedures to run .Net code inside the host process SQLServr.exe.

   In this case they are all Microsoft assemblies, and are tested by the DQS team, so we can ignore the warnings.

   SQL CLR’s restrictions cause this, and SQL CLR doesn’t have any switch to turn it off the warnings.

   Excerpt from C:\Program Files\Microsoft SQL Server\MSSQL11.InstanceName\MSSQL\Log\DQS_install.log

   [3/19/2012 9:30:20 PM] --> Registering Assemblies
[3/19/2012 9:30:20 PM]
[3/19/2012 9:30:20 PM] * Register .NET dependency assemblies
[3/19/2012 9:30:38 PM] Warning: The Microsoft .NET Framework assembly 'system.management, version=4.0.0.0, 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.
[3/19/2012 9:30:38 PM] Warning: The Microsoft .NET Framework assembly 'system.configuration.install, version=4.0.0.0, 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.
[3/19/2012 9:30:38 PM] Warning: The Microsoft .NET Framework assembly 'system.runtime.serialization, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, 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.
[3/19/2012 9:30:38 PM] Warning: The Microsoft .NET Framework assembly 'smdiagnostics, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, 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.
[3/19/2012 9:30:38 PM] Warning: The Microsoft .NET Framework assembly 'system.xaml, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, 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.
[3/19/2012 9:30:38 PM] Warning: The Microsoft .NET Framework assembly 'system.windows.forms, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, 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.
[3/19/2012 9:30:38 PM] Warning: The Microsoft .NET Framework assembly 'system.drawing, version=4.0.0.0, 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.
[3/19/2012 9:30:38 PM] Warning: The Microsoft .NET Framework assembly 'accessibility, version=4.0.0.0, 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.
[3/19/2012 9:30:38 PM] Warning: The Microsoft .NET Framework assembly 'system.runtime.serialization.formatters.soap, version=4.0.0.0, 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.
[3/19/2012 9:30:38 PM] Warning: The Microsoft .NET Framework assembly 'microsoft.jscript, version=10.0.0.0, 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.
[3/19/2012 9:30:39 PM] Warning: The Microsoft .NET Framework assembly 'system.management.instrumentation, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, 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.
[3/19/2012 9:30:40 PM] Warning: The Microsoft .NET Framework assembly 'system.messaging, version=4.0.0.0, 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.
[3/19/2012 9:30:40 PM] Warning: The Microsoft .NET Framework assembly 'system.directoryservices, version=4.0.0.0, 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly &soft .NET Framework assembly 'system.messaging, version=4.0.0.0, 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.
[3/19/2012 9#39;system.enterpriseservices, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=amd64.' 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'system.runtime.remoting, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'system.web, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=amd64.' 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.framework, version=4.0.0.0, 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'system.runtime.caching, version=4.0.0.0, 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.utilities.v4.0, version=4.0.0.0, 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'system.directoryservices.protocols, version=4.0.0.0, 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'system.design, version=4.0.0.0, 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'system.drawing.design, version=4.0.0.0, 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'system.web.regularexpressions, version=4.0.0.0, 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.tasks.v4.0, version=4.0.0.0, 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.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'system.serviceprocess, version=4.0.0.0, 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 workingoutine may stop working. Please refer SQL Server Books Online for more details.
[3/19/2012 9:30:59 PM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.tasks.v4.0, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitec. Please refer SQL Server Books Online for more details.
[3/19/2012 9:30:59 PM] * Register Microsoft.Practices assemblies
[3/19/2012 9:31:04 PM] Warning: The Microsoft .NET Framework assembly 'microsoft.csharp, version=4.0.0.0, 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.
[3/19/2012 9:31:04 PM] Warning: The Microsoft .NET Framework assembly 'system.dynamic, version=4.0.0.0, 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.
[3/19/2012 9:31:04 PM]
[3/19/2012 9:31:04 PM] * Register DQ assemblies
[3/19/2012 9:31:06 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.infra, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:07 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.core, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:08 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.dataservice, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:09 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.referencedata, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:10 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.index, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:11 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.associationrules, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:12 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.datavalueservice, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:13 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.domainrules, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:14 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.cleansing, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:15 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.association, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:16 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.flow, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:16 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs.matching, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[3/19/2012 9:31:18 PM] Warning: The SQL Server client assembly 'microsoft.ssdqs, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
   Return to Top

   ---

   Error when special character or accented character appears in TMP environment variable folder 

   When you run the DQSInstaller.exe to complete the installation of Data Quality Services in SQL Server 2012 RTM, the installation will fail if the TMP folder contains accented characters. This is common in non-english Windows account user names such as Accénted since the user profile and default Temp folder is located in a path with special characters by Windows itself.
   
   Excerpt from C:\Program Files\Microsoft SQL Server\MSSQL11.InstanceName\MSSQL\Log\DQS_install.log

   * Register Microsoft.Practices assemblies

   Msg 6501, Level 16, State 7, Server SERVERNAME, Line 2

   CREATE ASSEMBLY failed because it could not open the physical file 'c:\users\acc+énted\AppData\local\Temp\mwgl2t05.ltj\Microsoft.Practices.ObjectBuilder2.dll': 3(The system cannot find the path specified.).

   ERROR - An error occured, check message above

   Script process returned unexpected exit code: '1'.

   Action 'Register data quality assemblies and stored procedures' finished with errors, aborting installation.

   DQS Installer finished with errors. Please see installation log file at c:\Program Files\Microsoft SQL Server\MSSQL11.InstanceName\MSSQL\Log\DQS_install.log

   To resolve the situation where the user name has an accented character, please override the TMP environment variable temporarily in the command prompt session to run the DQSInstaller. Make a directory or use an existing directory, such as c:\temp, and set the TMP environment variable to point to that directory, then run DQSInstaller.exe from the same command prompt to set the local TMP variable to override the environment TMP variable. In this example MSSQLServer is the default instance of SQL Server, but the instance name may vary.
   
   Launch the command prompt as elevated administrator if on a UAC protected operating system. Start > cmd.exe > right click and Run as Administrator. Then run the following kind of command to begin DQSInstaller.exe, and follow the prompts to continue.

   
md C:\temp

   SET tmp=c:\temp

   cd "c:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLServer\MSSQL\Binn\"

   DQSInstaller.exe
   
   Return to Top
   

   ---

   Error: Cannot write into file 'dqs_certificate.cer'

   When you run the DQSInstaller.exe file to install Data Quality Server you might receive the following error:

   "Msg 15240, Level 16, State 2, Server SQL01\MSSQLSERVER, Line 1
   Cannot write into file 'dqs_certificate.cer'. Verify that you have write permissions, that the file path is valid, and that the file does not already exist."

   This occurs because there is already a file in the default DATA directory named dqs_certificate.cer from a previous failed installation or after you uninstalled DQS server. When you uninstall DQS server or a SQL Server instance containing DQS server, some DQS objects are not removed from the computer. You must manually delete this file after uninstalling DQS server or a SQL Server instance containing DQS server. To fix this issue:

   1. Exit the currently active DQS server installation by closing the DQSInstaller.exe window.
   2. Manually delete the existing dqs_certificate.cer file from the default DATA directory (usually C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA). For more information about removing DQS objects, see Remove Data Quality Services Objects.
   3. Run the DQSInstaller.exe file to reinstall DQS. For more information, see Run DQSInstaller.exe to Complete Data Quality Server Installation.

   This issue is corrected in Service Pack 1 for SQL Server 2012.

   Return to Top
   

   ---

   See Also

   • Installing Data Quality Services
   • Video: How Do I: Install and Configure DQS
   • Upgrade DQS: Installing Cumulative Updates or Hotfix Patches on Data Quality Services (en-US) 
   • Troubleshoot Operational Issues in Data Quality Services (DQS)
   • DQS Resources on TechNet Wiki