SQL Server 2008 ODBC Adapter Limitations

Supported Types

The types supported in this adapter are the following.

None.

Displaying table list
- Tables that exist in schemas other than dbo will be displayed as "<schema name>.<table name>".
NCHAR
- The end of NCHAR is not filled with spaces. (Behavior like variable-length)
IMAGE
- When the data is null, it is retrieved as 0 byte array (Binary type).
XML, VARCHAR(MAX), NVARCHAR(MAX), and VARBINARY(MAX)
- Retrieved up to 32767 bytes.
NTEXT
- Characters other than ASCII cannot be handled. Character corruption occurs.
The table name is case-insensitive even if it is enclosed with quotation marks.

NCHAR
- The beginning and end of NCHAR is not filled with spaces. (Behavior like variable-length data)
IMAGE
- When the data is null, it is retrieved as 0 byte array (Binary type).
XML, VARCHAR(MAX), NVARCHAR(MAX), and VARBINARY(MAX)
- Retrieved up to 32767 bytes.
NTEXT
- Characters other than ASCII cannot be handled. Character corruption occurs.

Displaying table list
- Tables that exist in schemas other than dbo will be displayed as "<schema name>.<table name>".
NCHAR
- The end of NCHAR is filled with spaces. (Behavior like fixed-length data)
DATETIME
- When DATETIME type is included in columns to write, batch update is not supported.
XML, VARCHAR(MAX), NVARCHAR(MAX), and VARBINARY(MAX)
- Retrieved up to 32767 bytes.
BIGINT
- When BIGINT type is included in columns to write, batch update is not supported.
TINYINT
- When TINYINT type is included in columns to write, batch update is not supported.
SMALLDATETIME
- When SMALLDATETIME type is included in columns to write, batch update is not supported.
The table name is case-insensitive even if it is enclosed with quotation marks.

In environment where the collation is SQL_Latin1_General_CP1_CI_AS, 2 byte characters written to nchar or nvarchar type column will be registered as “?”.

NCHAR
- The end of NCHAR is filled with spaces. (Behavior like fixed-length data)
DATETIME
- When DATETIME type is included in columns to write, batch update is not supported.
XML, VARCHAR(MAX), NVARCHAR(MAX), and VARBINARY(MAX)
- Retrieved up to 32767 bytes.
BIGINT
- When BIGINT type is included in columns to write, batch update is not supported.
TINYINT
- When TINYINT type is included in columns to write, batch update is not supported.
SMALLDATETIME
- When SMALLDATETIME type is included in columns to write, batch update is not supported.
In environment where the collation is SQL_Latin1_General_CP1_CI_AS, 2 byte characters written to nchar or nvarchar type column will be registered as “?”.

Not supported.

Not supported.

Exception name		Cause	Solution
java.sql.SQLException	[Microsoft][ODBC Driver Manager] Data source name and the specified default driver is not found.]	ODBC data source is not found.	Check [ODBC data source name] of the global resource.
	[Microsoft][SQL Native Client][SQL Server] User <user name> could not log in.	The user name or the password is incorrect.	Check [User name] or [Password] of the global resource.
	[Microsoft][SQL Native Client][SQL Server] Object name '<table name>' is invalid.	The table does not exist.	Specify an existing table in [Table name].
	[Microsoft][SQL Native Client][SQL Server] Syntax error exists around '<table name>'.	The table name may not be in accordance with the rules of Transact-SQL standard identifier.	Enclose the table specified in [Table name] with quotation marks.