Upgrade Data Quality Services
This article provides information on how to upgrade your existing installation of SQL Server Data Quality Services (DQS). As part of upgrading your SQL Server Data Quality Server, you must also upgrade the DQS databases schema.
- You must back up your DQS databases before upgrading DQS to prevent any accidental data loss during the schema upgrade. For information about backing up DQS databases, see Backing Up and Restoring DQS Databases.
- You can connect to SQL Server Data Quality Server by using the current or an earlier version of Data Quality Client or the DQS Cleansing Transformation in Integration Services to perform your data quality tasks.
- After upgrading Data Quality Services and Master Data Services, any earlier version of the Master Data Services Add-In for Excel will no longer work. You can download the SQL Server version of Master Data Services Add-In for Excel from here.
You must be logged on as a member of the Administrators group on the Data Quality Server computer.
Your Windows user account must be a member of the sysadmin fixed server role in the SQL Server instance where Data Quality Server is installed.
To upgrade DQS:
Back up your DQS databases before you start the upgrade process. For information about backing up DQS databases, see Backing Up and Restoring DQS Databases.
Upgrade the SQL Server instance where DQS is installed.
Run the SQL Server Setup wizard.
In the left pane, click Installation.
In the right pane, click Upgrade from... a previous version of SQL Server.
Complete the Setup wizard.
This will upgrade your SQL Server instance to SQL Server and also install the latest Data Quality Client, if Data Quality Client was previously installed on this computer. If you have Data Quality Client installed on other computers, you must run the sub steps in Step 2 on those computers to install the current version of Data Quality Client. The Setup wizard installs the current version of Data Quality Client alongside the existing version of Data Quality Client. After you upgrade the DQS databases schema, you can connect to the SQL Server version of Data Quality Server by using the current or an earlier version of Data Quality Client.
Upgrade the DQS databases schema.
Start Command Prompt as an administrator.
At the command prompt, change your directory to the location where DQSInstaller.exe is available. For the default instance of SQL Server, the DQSInstaller.exe file is available at C:\Program Files\Microsoft SQL Server\MSSQL[nn].MSSQLSERVER\MSSQL\Binn:
In the folder path, replace [nn] with the SQL Server version number.
- For SQL Server 2016: 13
- For SQL Server 2017: 14
``` cd C:\Program Files\Microsoft SQL Server\MSSQL[nn].MSSQLSERVER\MSSQL\Binn ```
At the command prompt, type the following command, and press ENTER:
The installer prompts you for backing up the DQS databases before proceeding. If you have already backed up your DQS databases, type Y or Yes, and then press ENTER to continue with the upgrade.
A completion message is displayed after successful upgrade of the DQS databases schema.
Verifying the DQS Databases Schema Upgrade
To verify that DQS databases schema have successfully upgraded, you can check the current version in the DQS_MAIN and DQS_PROJECTS databases by querying the A_DB_VERSION table in each database. To do so:
Start SQL Server Management Studio, and connect to the SQL Server instance that contains the upgraded DQS databases schema.
Run the following query:
SELECT * FROM DQS_MAIN.dbo.A_DB_VERSION WHERE STATUS=2; SELECT * FROM DQS_PROJECTS.dbo.A_DB_VERSION WHERE STATUS=2;
The output will display an entry for each upgrade along with the date of the upgrade. The maximum VERSION_ID and ASSEMBLY_VERSION on the latest date is the current version. A value of 2 in the STATUS column indicates success. If an error has occurred, the error will be listed in the ERROR column. A sample output:
ID UPGRADE_DATE VERSION_ID ASSEMBLY_VERSION USER_NAME STATUS ERROR 1000 2013-08-11 05:26:39.567 1200 11.0.3000.0 <DOMAIN\UserName> 2 1001 2013-09-19 15:09:37.750 1600 12.0.xxxx.0 <DOMAIN\UserName> 2