Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > SSL connections from DPA to SQL Server monitored instance

SSL connections from DPA to SQL Server monitored instance

Updated February 16, 2017


This article addresses the issue where a user is unable to connect to DPA to monitor a SQL Server instance that requires SSL connections.


  • All versions of DPA 
  • SQL Server monitored instance that requires a SSL connection
  • Steps are also below for SQL server repository databases that require and SSL connection


Update the connection information to get DPA to request the SSL connection. 

  1. In DPA, click Options > Update Connection Info.
  2. Select the SQL Server monitored instance that needs the SSL connection, and click Next.
  3. Select JDBC URL Properties, and add ssl=request

    If there are other entries in this field, you can add this with a semicolon as a separator. For example: NTLMv2=true;ssl=request. In some cases, customers are not reporting SSL connections.  Setting ssl=require fixes this. 


If the SQL server that holds DPA's repository is changed to require SSL then a similar flag needs to be added to the file that is has the DPA database connection string.  This is the file 


  1. Edit the file found in [DPA home]/iwc/tomcat/ignite_config/idc/ 
  2. Add one of the following repo.jdbcDriverProperties=useSSL\=request or perhaps repo.jdbcDriverProperties=useSSL\=require  depending on how restrictive the settings are for SSL on your server 
  3. save this file
  4. restart DPA 


Last modified