Knowledge Base >> Connecting to SQL Server using Named Pipes

Connecting to SQL Server using Named Pipes - Confio Article 1557

Confio Article: 1557 Published: Jun 11 2009 2:27 AM
Version: >=4.3.58 Topic(s): Install and Setup
Product(s): Ignite
Database(s): MS SQL

Overview

By default, Ignite connects to SQL Server instances via TCP/IP. If the SQL Server instance is not configured for TCP/IP connections or named pipes are preferred, Ignite can be configured to connect using named pipes by following the instruction below. Connections to an Ignite Repository on SQL Server using named pipes may provide better performance when the Ignite server resides on the same machine as the SQL Server instance.

 

Configuration

To enable Named Pipe connections in Ignite:

 

  1. Add the following property to <ignite_install_directory>/iwc/tomcat/ignite_config/idc/system.properties com.confio.idc.wizard.showAdditionalConnectionProperties=true
  2. If Ignite is running as a Windows service, the service must be reconfigured to run under a valid domain account (not the default Local System account). To change the account for the service, open the Services panel (Control Panel > Administrative Tools > Services), right click the Ignite PI Service and choose Properties. Under the tab "Log On", select the radio button "This account" and enter the credentials for a domain account.
  3. Restart the Ignite server
  4. When entering connection information, set the field "JDBC URL Properties" field to "namedPipe=true"

This process is the same for both Repository and monitored database connections.

 

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

repo.jdbcDriverProperties=namedPipe=true

 

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

 

Limitations

  • The driver used by Ignite 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 Ignite installations on non-Windows machines.
  • If Ignite is running as a Windows service, the service must be running under a valid domain account (i.e., not Local System account). 
     

 

Tags: upgrade service sql server login failed connection tcp named pipe domain account