Configuring QuerySurge Connections: SQL Server
When you create a QuerySurge Connection, the Connection Wizard will guide you through the process. Different types of QuerySurge connections require different types of information.
For an SQL Server Connection, you will need the following information (check with a DBA or other knowledgeable resource in your organization):
- Database login credentials (ID and Password)
- Server Name or IP address of the SQL Server (e.g. sqlsvr1.myserver.com, or 192.168.0.255)
- The Port for your SQL Server database (1433 is the default port)
- The Database name
Launch the Connection Wizard
- Log into QuerySurge as an Admin user.
- To configure a Connection, select Configuration > Connection in the Administrative View tree (at the left).
- Click on the Add button at the bottom left of the page to launch the Connection Wizard. Click Next.
Note: Check the Advanced Mode checkbox for access to advanced features.
- Provide a name for your connection. Select SQL Server as the Data Source. Click Next.
Note: An SQL Server JDBC driver is bundled with QuerySurge, so you can install this driver from the QuerySurge Installer.
- Once you have selected your Data Source, the Wizard will tell you what information you are likely to need in order to create your Connection. Once you have collected this information, you are ready to click Next.
Note: This document describes setup for SQL Server with Database Authentication. For instructions on setting up SQL Server using Windows Authentication, see the companion document.
- Provide the connection information to your database. This includes the Server name or IP address, the Port (the default port for your database product will automatically populate), the Database name and the login credentials. Click Next.
Required fields for your Connection Type are marked by an *.
- Click on Test Connection.
Note: You must have an Agent running with the driver for this Connection deployed in order to test the Connection.
- Save the Connection.
- Congratulations! You’ve created a QuerySurge Connection. Make sure that you have deployed the driver for this Connection to all your QuerySurge Agents. (See Adding a JDBC Driver to your QuerySurge Agent for instructions.)