When adding a connector to a fabric, QueryGrid performs the following tasks on the Teradata system initiating nodes:
- Creates the directories required for completing the installation
- Installs the Teradata connector package. The Teradata connector package includes the following:
- A stored procedure that provides a simple interface for executing basic SQL queries
- Push profile code, associated functions, and macros that allow you to use Remote Table Optimization (RTO) with QueryGrid
This procedure includes the following:
- Running an installation script to unpack and distribute the Teradata connector package components
- Additional setup steps
- Make sure the connector package has been downloaded from Teradata's software download site and uploaded to the QueryGrid portlet, and that the connector has been added to the fabric.
- Under Fabric Configuration, select Fabrics.
- Select the fabric containing the Teradata initiating nodes.
- Select Connectors tab.
- Select
next to the Teradata initiating connector for the Teradata system nodes and select Install.
- From Connector Installation, select one of the following:
- Active
- Pending
- In the Select driver node list, select the driver node to run the installation script.
- To allow the installation script to run, provide the Username and Password logon for an Administrator, such as DBC, of the initiating Teradata system.
- In the Transaction Mode list, select one of the following:The mode determines how a stored procedure can be run.
Option Description For systems running in Teradata mode: Select TERA. For systems running in ANSI mode: Select ANSI. - Select Run.The stored procedure and RTO components are installed on all the Teradata system nodes.
- Verify successful installation by checking that the driver node specified in the Select driver node list is represented in the Success field.
- [Optional] Verify the stored procedure is installed on the Teradata system nodes.
- Log on as an Administrator, such as DBC, of the initiating Teradata system.
- Create the related foreign server.
For example:
CREATE FOREIGN SERVER target_server_name_efssp EXTERNAL SECURITY DEFINER TRUSTED target_server_auth USING LINK('linkname') VERSION ('version’) DO IMPORT WITH TD_SYSFNLIB.QGExecuteForeignQuery;
- From td_server_db, grant the SELECT privilege on the target server to initiating end users.
For example:
GRANT SELECT on td_server_db.target_server_name_efssp to initiating_end_user;
- Submit the DDL or DCL query on the target system.
For example:
.logon initiating_end_user, initiating_end_user CALL SYSLIB.ExecuteForeignSQL(‘DDL’, ‘target_server_name_efssp’);