When comparing Adaptive Server column types and lengths with the metadata obtained from a remote server, Unicode datatypes in the proxy table are allowed under the following circumstances:
The remote server datatype for a column is unichar, unitext, or univarchar with equal length (expressed in characters, not bytes).
The remote server datatype for a given column is char or varchar. In this case, Component Integration Services performs conversions to Unicode on data fetched from the remote server, and conversions from Unicode to the default Adaptive Server character set (UTF8) on data transmitted as part of DML commands (select, insert, delete, update).
The remote server datatype for a Unicode column is binary or varbinary. The length of the remote server column must be twice the length of the Unicode column. Component Integration Services performs conversions as required when transmitting data to or from the remote server.
No other datatype mapping for Unicode datatypes is allowed when mapping a proxy table to a remote table. Other types result in a type mismatch error. You can convert data from legacy systems into Unicode simply by creating a proxy table that maps a Unicode column to an existing char or varchar column.
Unicode can only be mapped to unitext columns using
the create existing table command.
