Applications Systems

Move a DPA repository on SQL Server to Azure SQL

This article explains how to move a DPA repository from an on-premises SQL Server instance to an Azure SQL instance in the cloud.

First published date

11/1/2018 6:25 PM

Last published date

9/10/2025 9:18 PM

Overview

This article provides steps to move a DPA repository from an on-premises SQL Server instance to an Azure SQL instance in the cloud.

If you need to move a SQL Server, Oracle, or MySQL repository, see the following:

Product section

Database Performance Analyzer

Resolution

Prerequisites 

This article assumes that the target Azure SQL database instance is not created yet.

Make sure that:

  • The SQL Server database instance is compatible with the Azure SQL database version

For more information:

After migration of the database with one of the methods listed take the following steps to connect DPA to the migrated repository. 

  1. Specify the Azure SQL database settings. See DPA Requirements  for the supported Azure SQL database tiers. Make sure requirements are met or performance maybe poor. 
  2. In DPA, click Stop All Monitors in the upper right.
  3. Shut down DPA.
    • Windows: Stop the IgnitePI service.
    • Linux: Run shutdown.sh in the DPA installation directory. Ensure there are no crontab entries that will restart DPA.
  4. On the DPA server, open the repo.properties file in a text editor.
    • Windows: This file is located at DPA_install_dir\iwc\tomcat\ignite_config\idc
    • Linux: This file is located at DPA_home/iwc/tomcat/ignite_config/idc
  5. Edit the values for the following lines to point to the new repository: two values must change repo.databaseType and repo.jdbcDriverName. Other values that might change depending on enviroment are repo.jdbcDriverProperties= 
    repo.databaseType=Azure SQL Database
repo.jdbcDriverName=AzureSQLDriver
    repo.databaseName=
repo.host=
repo.user=
repo.password=
    # SQL authentication accounts tend to use the following settings 
    repo.jdbcDriverProperties=authentication\=NotSpecified;encrypt\=true;trustServerCertificate\=true
    # Users for the connection as EntraID domain accounts tent to use the following settings when using password
    repo.jdbcDriverProperties=authentication=\ActiveDirectoryPassword;encrypt\=true;trustServerCertificate\=true
  6. Start DPA.
    • Windows: Start the IgnitePI service.
    • Linux: Run startup.sh in the DPA installation directory.
  7. In DPA, make sure the server connects to the new Azure SQL repository database.
  8. Review the status of the database monitors, and start or stop them accordingly.
  9. Review the DPA log for errors.
  10. Wait for 10 minutes, and drill down into each monitored database instance.
  11. Make sure that you see data from the last 10 minutes for the database instances.

Troubleshooting 

The database compatibility level must be set to 130 (for V12 template). See the following KB article from Microsoft:

Delete all unnecessary users.

  • Delete all users with Windows authentication.
  • Disable or delete the guest user. When you delete this user, it will be created again but with a disabled login.
  • If on Startup you see errors for permissions not grated on a table and or schema it could be your database tables are in dbo or ignite for the schema  for example [select V from CONPRM where P = ?]; SQL state [S0005]; error code [229]; The SELECT permission was denied on the object 'CONPRM', database 'Dpa', schema 'dbo'.;