QueryGrid 2.x Teradata connectors are compatible with the SQL data manipulation language used for QueryGrid 1.x Teradata-to-X connectors. In QueryGrid 2.x, if you want to use the same SQL you use with your 1.x connectors, you can migrate your 1.x foreign server definitions for use with 2.x connectors.
The following procedure preserves the FOREIGN SERVER grants and access rights for users.
- Stop all queries running on the QueryGrid 1.x foreign server.
- For the FOREIGN SERVER used on QueryGrid 1.x, type the following to display the FOREIGN SERVER description, the list of custom clauses, and the import and export functions used for the FOREIGN SERVER:
SHOW FOREIGN SERVER bock_classic2; CREATE FOREIGN SERVER TD_SERVER_DB.bock_classic2 EXTERNAL SECURITY INVOKER TRUSTED UT1PROXY3 USING Hosttype ('Teradata') remotehost ('bock1.labs.teradata.com') ip_device ('byn1') port ('5000') read_timeout (200 ) listen_timeout (60 ) concurrentstreams (1 ) DO IMPORT WITH SYSLIB.LOAD_FROM_TD , DO EXPORT WITH SYSLIB.LOAD_TO_TD ; - Drop all old NVPs from the QueryGrid 1.x foreign server.
ALTER FOREIGN SERVER TD_SERVER_DB.bock_classic2 DROP hosttype, drop remotehost, drop ip_device, drop port, drop read_timeout, drop listen_timeout, drop concurrentstreams, drop IMPORT, drop EXPORT;
- Add the new NVPs to the QueryGrid 1.x foreign server.
ALTER FOREIGN SERVER TD_SERVER_DB.bock_classic2 ADD link(‘bock_ng’), add IMPORT WITH TD_SYSFNLIB.QGINITIATORIMPORT, add export with TD_SYSFNLIB.QGINITIATOREXPORT;
- Show the new QueryGrid 2.x FOREIGN SERVER.
SHOW FOREIGN SERVER bock_classic2; CREATE FOREIGN SERVER TD_SERVER_DB.bock_classic2 EXTERNAL SECURITY INVOKER TRUSTED UT1PROXY3 USING LINK(‘bock_ng’) DO IMPORT WITH TD_SYSFNLIB.QGINITIATORIMPORT, DO EXPORT WITH TD_SYSFNLIB.QGINITIATOREXPORT;
For more information about configuring the 2.x foreign server with QueryGrid 2.x name value pairs, see: