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.
- •Do not use an ODBC connection for databases that have predefined connection types. 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.
- •ODBC connections do not support Unicode (UTF-8) data. No tasks can read or write Unicode data using an ODBC connection.
- •Do not use data filter variables with ODBC source connections.
- •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).
- •If you use an ODBC connection for an Excel target, data is inserted into the target. The ODBC driver does not allow you to update or delete existing Excel data.
- •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 Configuration tasks, use an advanced relationship instead of an existing or custom relationship.
In Data Synchronization tasks, use a user-defined join.