SQL Server Data Quality Services (DQS) is a new feature in SQL Server 2012 that contains the following two components: Data Quality Server and Data Quality Client.
Data Quality Server
Data Quality Server is installed on top of the SQL Server 2012 Database Engine, and includes three databases: DQS_MAIN, DQS_PROJECTS, and DQS_STAGING_DATA. DQS_MAIN contains DQS stored procedures, the DQS engine, and published knowledge bases. DQS_PROJECTS contains the data quality project information. DQS_STAGING_DATA is the staging area where you can copy your source data to perform DQS operations, and then export your processed data.
Data Quality Client
Data Quality Client is a standalone application that enables you to connect to Data Quality Server, and provides you with a highly-intuitive graphical user interface to perform data-quality operations, and other administrative tasks related to DQS.
Apart from the above two DQS components, there is a DQS Cleansing component in Integration Services that performs data cleansing within the Integration Services packaging process, and is automatically installed when you install Integration Services. For information about installing Integration Services, see Install Integration Services.
You can also enable DQS integration in Master Data Services to use the DQS matching functionality in the Master Data Services Add-in for Excel. For more information, see Enable Data Quality Services Integration with Master Data Services.
DQS installation is a three-part process:
Pre-Installation Tasks: Verify system requirements before you install DQS.
Data Quality Services Installation Tasks: Install DQS by using SQL Server Setup.
Post-Installation Tasks: Perform these tasks after finishing with the SQL Server Setup to finish installing DQS.
Before installing DQS, make sure that your computer meets the minimum system requirements. The following table provides information about the minimum system requirements for the DQS components:
Minimum System Requirements
Data Quality Server
Data Quality Client
For detailed information about the minimum system requirements for installing SQL Server 2012, see Hardware and Software Requirements for Installing SQL Server 2012.
You have to use the SQL Server 2012 Setup to install DQS components. When you run the SQL Server Setup, you have to go through a series of installation wizard pages to select appropriate options based on your requirements. The following table lists only those pages in the installation wizard where the options that you select will affect your installation of DQS:
Database Engine Configuration
Click Add Current User to add your user Windows account to the sysadmin fixed server role. This is required for you to be able to run the DQSInstaller.exe file later to complete the Data Quality Server installation.
After you complete the SQL Server installation wizard, you must perform additional steps mentioned in this section to complete your Data Quality Server installation, configure it, and then use it.
Complete the Data Quality Server installation
Run the DQSInstaller.exe file. On running the DQSInstaller.exe file:
This completes the Data Quality Server installation.
Grant DQS Roles to Users
To log on to Data Quality Server using Data Quality Client, a user must have any of the following three roles on the DQS_MAIN database: dqs_administrator, dqs_kb_editor, or dqs_kb_operator. By default, if your user account is a member of the sysadmin fixed server role, you can log on to Data Quality Server using Data Quality Client even if none of the DQS roles are granted to your user account. For information about the three DQS roles, see DQS Security.
Enable the TCP/IP network protocol if Data Quality Server will be accessed from a remote computer
If the Data Quality Server and Data Quality Client components are not on the same computer, you must enable the TCP/IP protocol for the SQL Server instance where Data Quality Server is installed using SQL Server Configuration Manager. Otherwise, the remote Data Quality Client applications cannot connect to Data Quality Server.
Make your data available for DQS operations
Make sure that you can access your source data for the DQS operations, and can export the processed data to a table in a database.