SQL Server 2005 ODBC Adapter Limitations

• Supported Types
• Common to all processing
• Read Table
• Execute Select SQL
• Write table
• Execute Update SQL
• Execute Stored Procedure
• Write by Loader
• Main exceptions

Supported Types

• Yes: Support.
• Limited: Support with limitations.
• No: Not supported.

Common to all processing

Specification Limits

Read Table

• Table List View
  • Table with schema other than dbo schema is shown as <schema name>.<table name>.
• NCHAR
  • Can get without pending spaces at the end. (Behavior similar to variable length)
• IMAGE
  • If data is null, get as zero-length byte array(binary type).
• XML, VARCHAR(MAX), NVARCHAR(MAX), VARBINARY(MAX)
  • Can get up to 32767 bytes.
• NTEXT
  • none ascii character cannot be used. Characters will be garbled.
• Upper/lower case is not distinguished in table name even when table name is enclosed in quotation marks.

Execute Select SQL

• NCHAR
  • Can get without pending spaces at the end. (Behavior similar to variable length)
• IMAGE
  • If data is null, get as zero-length byte array(binary type).
• XML, VARCHAR(MAX), NVARCHAR(MAX), VARBINARY(MAX)
  • Can get up to 32767 bytes.
• NTEXT
  • none ascii character cannot be used. Characters will be garbled.

Write table

• Table List View
  • Table with schema other than dbo schema is shown as <schema name>.<table name>.
• NCHAR
  • Padding with spaces (Behavior similar to fixed length)
• XML, VARCHAR(MAX), NVARCHAR(MAX), VARBINARY(MAX)
  • Can get up to 32767 bytes.
• BIGINT
  • Batch update is not supported when the type of the column to write contains BIGINT type.
• TINYINT
  • Batch update is not supported when the type of the column to write contains TINYINT type.
• Upper/lower case is not distinguished in table name even when table name is enclosed in quotation marks.


• In environment with collation of SQL_Latin1_General_CP1_CI_AS, if nchar type, nvarchar type column is written with double-byte characters, it is registered as "?".

Execute Update SQL

• NCHAR
  • Padding with spaces (Behavior similar to fixed length)
• XML, VARCHAR(MAX), NVARCHAR(MAX), VARBINARY(MAX)
  • Can write up to 32767 bytes.
• BIGINT
  • Batch update is not supported when the type of the column to write contains BIGINT type.
• TINYINT
  • Batch update is not supported when the type of the column to write contains TINYINT type.
• In environment with collation of SQL_Latin1_General_CP1_CI_AS, if nchar type, nvarchar type column is written with double-byte characters, it is registered as "?".

Execute Stored Procedure

Write by Loader

Main exceptions