Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Database Performance Analyzer (DPA) > Connect to SQL Server using named pipes

Connect to SQL Server using named pipes

Created by Interspire Import, last modified by Anthony.Rinaldi_ret on Jul 12, 2016

Views: 310 Votes: 0 Revisions: 15

Overview

By default, DPA connects to SQL Server instances through TCP/IP. If the SQL Server instance is not configured for TCP/IP connections or named pipes are preferred, you can configure DPA to connect using named pipes by following the instruction below. Connections to a DPA repository on SQL Server using named pipes may provide better performance when the DPA server resides on the same computer as the SQL Server instance.

Limitations

  • The driver DPA uses for SQL Server connections does not support the named pipe at a location other than /sql/query on the server.
  • Named pipe connections are not supported for DPA installations on non-Windows machines.
  • If DPA is running as a Windows service, the service must be running under a valid domain account. In other words, not the local system account.

Environment

  • DPA 9.0 and later

Steps

  1. If DPA is running as a Windows service, you must reconfigure the service to run under a valid domain account, and not the default local system account. To change the account for the service:
    1. Open the Services panel (Control Panel > Administrative Tools > Services).
    2. Right-click the Ignite PI Service, and click Properties.
    3. Click the Log On tab, click This account, and then enter the credentials for a domain account.
    4. Restart the Ignite PI Service.
  2. When entering connection information, click the Advanced Connections Property link, and enter namedPipe=true in the JDBC URL Properties field.

 

This process is the same for repository and monitored database instance connections.

 

If the repository has already been created, you can change the connection to use named pipes by adding the following line to (or updating the existing property in) the <install_directory>/iwc/tomcat/ignite_config/idc/repo.properties file located in the following directory:

 

repo.jdbcDriverProperties=namedPipe=true

 

To use named pipes when connecting to a monitored SQL Server instance, run the Update Monitored Database Connection wizard on the Options page. Check the box labeled JDBC URL Properties and enter the namedPipe=true property as shown above.

Last modified
07:22, 12 Jul 2016

Tags

Classifications

Public