Azure SQL Database Adapter Limitations

Supported Types
Common to all processing
Read Table
Execute Select SQL
Write Table
Execute Update SQL
Main exceptions

Supported Types

This adapter supports types as follows.

Type name	Support	Remarks
BIGINT	Yes
INT	Yes
SMALLINT	Yes
TINYINT	Yes
BIT	Yes
NUMERIC	Yes
DECIMAL	Yes
MONEY	Yes
SMALLMONEY	Yes
FLOAT	Yes
REAL	Yes
TIME	No
DATE	No
SMALLDATETIME	Yes
DATETIME	Limited
DATETIME2	No
DATETIMEOFFSET	No
CHAR	Limited
VARCHAR	Limited
NCHAR	Yes
NVARCHAR	Yes
TEXT	Limited
NTEXT	Yes
BINARY	Yes
VARBINARY	Yes
IMAGE	Yes
VARCHAR(MAX)	Limited
NVARCHAR(MAX)	Yes
VARBINARY(MAX)	Yes
XML	Yes
SQL_VARIANT	No
UNIQUEIDENTIFIER	No

Yes: Support.
Limited: Support with limitations.
No: Not support

Common to all processing

Specification Limits

Databases with names containing the following characters cannot be specified. Databases with names containing characters other than the following still may cannot be specified.
Contact the database vendor for more information.
- "{"
- ";"
If you run several processes of this adapter in the same transaction, the connection may time out after 5 minutes by the Microsoft Azure SQL Database specification limit.

Notes

This adapter connects to Microsoft Azure SQL Database with SSL.

Read Table

Specification Limits

Table List View
- Table with schema other than dbo schema is shown as <schema name>.<table name>.
Upper/lower case is not distinguished in table name even when table name is enclosed in quotation marks.

Execute Select SQL

None.

Write Table

Specification Limits

Table List View
- Table with schema other than dbo schema is shown as <schema name>.<table name>.

DATETIME

Value in milliseconds unit will be rounded when data specified in milliseconds is inserted.Millisecond value is rounded to 0ms, 3ms, or 7ms.

Example	Rounded result
01/01/98 23:59:59.999	1998-01-02 00:00:00.000
01/01/98 23:59:59.995, 01/01/98 23:59:59.996, 01/01/98 23:59:59.997 or 01/01/98 23:59:59.998	1998-01-01 23:59:59.997
01/01/98 23:59:59.992, 01/01/98 23:59:59.993, 01/01/98 23:59:59.994	1998-01-01-23:59:59.993
01/01/98 23:59:59.990 or 01/01/98 23:59:59.991	1998-01-01 23:59:59.990

CHAR, VARCHAR, TEXT, VARCHAR (MAX)
- Multi-byte characters are not supported.
Upper/lower case is not distinguished in table name even when table name is enclosed in quotation marks.

Execute Update SQL

DATETIME

Value in milliseconds unit will be rounded when data specified in milliseconds is inserted.Millisecond value is rounded to 0ms, 3ms, or 7ms.

Example	Rounded result
01/01/98 23:59:59.999	1998-01-02 00:00:00.000
01/01/98 23:59:59.995, 01/01/98 23:59:59.996, 01/01/98 23:59:59.997 or 01/01/98 23:59:59.998	1998-01-01 23:59:59.997
01/01/98 23:59:59.992, 01/01/98 23:59:59.993, 01/01/98 23:59:59.994	1998-01-01-23:59:59.993
01/01/98 23:59:59.990 or 01/01/98 23:59:59.991	1998-01-01 23:59:59.990

CHAR, VARCHAR, TEXT, VARCHAR (MAX)
- Multi-byte characters are not supported.

Main exceptions

Exception name		Causes	Solution
com.microsoft.sqlserver.jdbc.SQLServerException	user <username> Login failed.	Either User name or Password is invalid.	Please confirm [User name] or [Password] in Global Resource. And confirm that the format of the user name is <user name>@<server name>.
	The TCP/IP connection to the host <server name>.database.windows.net, port 1433 has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.".	Either Database name or User name is invalid.	Please confirm [Database name] or [User name] in Global Resource. And confirm that the format of the user name is <user name>@<server name>.
	Connection reset	Either User name is invalid.	Please confirm that the format of the user name is <user name>@<server name>.
	Server name cannot be determined. It must appear as the first segment of the server's dns name (servername.database.windows.net). Some libraries do not send the server name, in which case the server name must be included as part of the user name (user name@server name). In addition, if both formats are used, the server names must match.	Either User name is invalid.	Please confirm that the format of the user name is <user name>@<server name>. And confirm that the server name is valid.
	The TCP/IP connection to the host <host name>, port 1433 has failed. Error: "null. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.".	Cannot connect to the database.	Check the network connectivity and ensure the [Hostname] specified is valid.
	Cannot open database "<database name>" requested by the login. The login failed.	"<database name>" does not exist.	Please confirm [Database name] in Global Resource.
	Invalid object name '<table name>'	"<table name>" does not exist.	Please confirm [Table name].
	Incorrect syntax near '<table name>'	The table name may not follow the rules for standard identifiers of Transact-SQL.	In that case, enclose [Table name] with quotation marks.