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 rules and guidelines

ODBC connection rules and guidelines

Consider the following rules and guidelines when you create an ODBC connection:
  • ODBC connections support system DSNs, not user DSNs.
  • It is recommended to use a predefined connection instead of an ODBC connection for databases. For example, use the Oracle connection type to connect to an Oracle database.
  • When you create or edit a task with an ODBC connection, database tables from other schema in the database might appear in the wizard. The wizard does not filter tables based on the schema specified for the ODBC connection.
  • Even though you can use an ODBC connection to read
    or write
    unicode data, ensure that source
    or target
    table names and field names do not contain Unicode (UTF-8) characters.
  • The data preview area might not display data from an ODBC connection if the database table or column name is also a database key word.
  • If you use an ODBC connection for an Oracle database target, ensure that Oracle table columns with the following data types do not exceed the specified maximum precision: char(1999), varchar(3999), nvarchar(3998), and nchar(3998).
  • You can't use an ODBC connection to perform update or delete operation on an Excel target.
  • If you use an ODBC connection for an Excel source
    or target
    file, ensure that named ranges are defined in the Excel file.
  • Do not use an ODBC connection to perform upserts on a MySQL database. Use a MySQL connection to perform upserts.
  • When you use an ODBC connection to include multiple MySQL tables in
    mapping
    tasks, use an advanced relationship instead of an existing or custom relationship.
  • In
    synchronization
    tasks, use a user-defined join.
  • The Snowflake ODBC driver is not applicable for SUSE Linux.
  • When you use a saved query, do not specify a star ( * ) in the projection list in a saved query. For example, in
    SELECT * from EMP_MVIEW
    , instead of star, you must specify the columns explicitly in the query.
  • When you use an ODBC connection with the subtype as DB2, you cannot perform the following operations:
    • Override the default update SQL statement to write to a DB2 target.
    • Configure an SQL transformation to call a stored procedure.

0 COMMENTS

We’d like to hear from you!