Overview

By default, when creating a repository in SQL Server or registering a SQL Server instance to be monitored, Ignite connects via TCP/IP. If needed, Ignite can be configured to connect using named pipes by following the instructions below.

Note: Connections to an Ignite Repository on SQL Server using named pipes may provide better performance when the Ignite PI Server and repository are located on the same machine.

Configuration

1. In the Database Instance Registration or Repository Creation Wizard, click the Advanced Connection Properties link.

2. Enter "namedPipe=true" in the JDBC URL Properties text box.

3. Ignite will now use Named Pipes to connect to the SQL Server instance.

Use Named Pipes by Default

If the Repository has already been created, the connection can be changed to use named pipes for all new database registrations 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

Updating an Existing Database to use Named Pipes

To use named pipes when connecting to an existing 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).