Table of Contents

Search

  1. Preface
  2. Introduction to ODBC Connector
  3. ODBC connections
  4. Synchronization tasks with ODBC Connector
  5. Mappings and mapping tasks with ODBC Connector
  6. SQL ELT optimization
  7. Data type reference

ODBC Connector

ODBC Connector

ODBC connection properties

ODBC connection properties

When you set up an ODBC connection, configure the connection properties.
The following table describes the ODBC connection properties:
Property
Description
Runtime Environment
The name of the runtime environment where you want to run the tasks.
Specify a Secure Agent, Hosted Agent, or serverless runtime environment.
ODBC Subtype
The ODBC connection subtype that you must select to connect to a specific database. The subtype defines the capabilities that you can configure while you create a mapping.
You can select from the following supported subtypes based on the database to which you want to connect:
  • Azure DW. Select Azure DW to enable
    SQL ELT optimization
    when you read from
    or write to
    Microsoft Azure SQL Data Warehouse.
  • DB2. Select DB2 to read from
    or write to
    DB2. You can also enable
    SQL ELT optimization
    when you read from
    or write to
    DB2.
  • Google BigQuery. Select Google BigQuery to enable
    SQL ELT optimization
    when you read from
    or write to
    Google BigQuery.
  • PostgreSQL. Select PostgreSQL to enable
    SQL ELT optimization
    when you read from
    or write to
    PostgreSQL.
  • Redshift. Select Redshift to enable
    SQL ELT optimization
    when you read from
    or write to
    Amazon Redshift.
  • SAP IQ. Select SAP IQ to read data from the SAP IQ database.
  • Snowflake. Select Snowflake to enable
    SQL ELT optimization
    when you read from
    or write to
    Snowflake.
  • Teradata. Select Teradata to enable
    SQL ELT optimization
    when you read from
    or write data to
    Teradata. You can also enable SQL transformation in a mapping to call a stored procedure in Teradata or to process SQL saved queries against the Teradata database.
    If you want to connect to an SSL-enabled ODBC Teradata connection, ensure that the
    SSL Mode
    option under
    WebSocket
    is set to an appropriate value while configuring the Teradata ODBC driver.
  • Other. Select Other to enable
    SQL ELT optimization
    when you read from
    or write to
    Microsoft Access, Microsoft Excel, or Netezza.
Authentication Mode
The authentication method to connect to DB2.
This property appears only if you select the ODBC subtype as
DB2
.
Select one of the following authentication modes from the list:
  • Database. Uses your DB2 user name and password to connect to DB2.
  • Kerberos. Uses Kerberos authentication to connect to DB2.
    When you choose this option on Windows, ensure that the user account that starts the Secure Agent service is available in the DB2 database. You don't need to enter your credentials to access DB2.
    You can't configure Kerberos authentication when you use a Hosted Agent or serverless runtime environment.
    Default is Database.
Kerberos Connection Properties
Additional connection properties to use Kerberos authentication to connect to DB2.
This property appears only if you select the ODBC subtype as
DB2
and authentication mode as
Kerberos
.
If you specify more than one property, separate each key-value pair with a semicolon.
For example, if you don't set the required environment variables on the Secure Agent machine before you use Kerberos authentication, add the
KRB5CONFIG
and
KRB5CCNAME
properties in the following format:
KRB5CONFIG=<Absolute path of the Kerberos configuration file>\krb5.conf;KRB5CCNAME=<Absolute path of the credential cache file>/<File name>
User Name
User name for the database login.
Password
Password for the database login. The password cannot contain a semicolon.
Data Source Name
System DSN.
Schema
Schema used for the object.
Code Page
The code page of the database server or flat file defined in the connection. Select one of the following code pages:
  • MS Windows Latin 1. Select for ISO 8859-1 Western European data.
  • UTF-8. Select for Unicode data.
  • Shift-JIS. Select for double-byte character data.
  • ISO 8859-15 Latin 9 (Western European).
  • ISO 8859-2 Eastern European.
  • ISO 8859-3 Southeast European.
  • ISO 8859-5 Cyrillic.
  • ISO 8859-9 Latin 5 (Turkish).
  • IBM EBCDIC International Latin-1.
  • Japanese Extended UNIX Code (incl. JIS X 0212)
  • Japanese EUC (with \<-> Yen mapping)
  • Japanese EUC (Packed Format)
  • IBM EBCDIC Japanese
  • IBM EBCDIC Japanese CP939
  • Japanese EBCDIC Fujitsu
  • HITACHI KEIS Japanese
  • NEC ACOS JIPSE Japanese
  • UNISYS Japanese
  • MITSUBISHI MELCOM Japanese
  • Japanese EBCDIC-Kana Fujitsu
  • HITACHI KEIS-Kana Japanese
  • NEC ACOS JIPSE-Kana Japanese
  • UNISYS-Kana Japanese
  • MITSUBISHI MELCOM-Kana Japanese
  • EBCDIC Japanese
  • EBCDIK Japanese
  • PC Japanese SJIS-78 syntax (IBM-942)
  • PC Japanese SJIS-90 (IBM-943)
  • EBCDIC Japanese Katakana SBCS
  • EBCDIC Japanese Katakana (w/ euro)
  • EBCDIC Japanese Latin-Kanji (w/ euro)
  • EBCDIC Japanese Extended (DBCS IBM-1390 combined with DBCS IBM-1399)
  • EBCDIC Japanese Latin (w/ euro update)
  • EBCDIC Japanese Katakana SBCS (w/ euro update)
  • MS Taiwan Big-5 w/ HKSCS extensions
  • MS Windows Traditional Chinese, superset of Big 5
  • Taiwan Big-5 (w/ euro update)
  • Taiwan Big-5 (w/o euro update)
  • PC Chinese GBK (IBM-1386)
  • Chinese EUC
  • Simplified Chinese (GB2312-80)
  • Hong Kong Supplementary Character Set
  • ISO 8859-8 Hebrew
  • PC Hebrew (old)
  • PC Hebrew (w/o euro update)
  • PC Hebrew (w/ euro update)
  • MS Windows Hebrew (older version)
  • MS Windows Hebrew (w/o euro update)
  • Lotus MBCS encoding for Windows Hebrew
  • EBCDIC Hebrew (updated with sheqel, control characters)
  • EBCDIC Hebrew (w/ euro)
  • EBCDIC Hebrew (updated w/ euro and new sheqel, control characters)
  • Israeli Standard 960 (7-bit Hebrew encoding)
Driver Manager for Linux
When you create a new ODBC connection on Linux platform, you can select a driver manager for the Linux Secure Agent. Select one of the following driver managers:
  • Data Direct
  • unixODBC2.3.0
  • unixODBC2.3.4
The default driver manager is UnixODBC2.3.0.
To connect to Teradata, you can use only Data Direct as the driver manager on Linux.

0 COMMENTS

We’d like to hear from you!