Configuring Query Surge Connections: IBM PureData System for Analysis (Netēzza) When you create a QuerySurge Connection, the Add Connection Wizard will guide you through the process. Different types of QuerySurge connections require different types of information. For a Connection to IBM PureData System for Analysis (IPDA), formerly called Netēzza, 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 IPDA Server (e.g. Analytics.finance.com, or 192.168.0.255) The Port for your IPDA database (5480 is the default port) The IPDA Database name Launch the Add Connection Wizard 1.
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 Add Connection Wizard.
Netezza System Administrator Guide
Note: Check the Advanced Mode checkbox for access to advanced features. Provide a name for your connection. Select IPDA (Netēzza) as the Data Source. Note: The IPDA JDBC driver is not bundled with QuerySurge, so you will need to install the driver with all your Agents. See for instructions. 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.
Netezza System Date
Once you have collected this information, you are ready to click Next. 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 login credentials. Required fields for your Connection Type are marked by an. Click on Test Connection.
Netezza System Catalog Tables
Note: You must have an Agent running with the driver for this Connection deployed in order to test the Connection. Save the connection 9. You’ve created a QuerySurge Connection.
Again, make sure that you have deployed the driver for this connection to all your QuerySurge Agents (see #4 above).