Filter:
Submit Search

Messages and limitations of the Azure SQL Database connector

Message code list of SQLAZURE category

The following message codes correspond to errors that occur in Azure SQL Database Connector.

 

SQLAZURE0000E

This message code is output when an undefined error occurs.

Cause

Solution

An undefined error occurred.

Check the error message or the help of the operation in which the error has occurred.

Corresponding error

  • None

 

SQLAZURE0001E

This message code corresponds to errors that occur during database processing.

Cause

Solution

The cause differs according to each error message.

Check the error message and perform the following:

  • Check whether the cause/solution of the error is described in "Exception messages" below.

  • Check whether the cause/solution of the error is described in Limitations of the applied connector.

  • Check whether you can find information related to the error in documents of the connected database.

Corresponding error

  • java.sql.SQLException

  • com.microsoft.sqlserver.jdbc.SQLServerException

 

Exception messages of SQLAZURE category

Exception name

Cause

Solution

com.microsoft.sqlserver.jdbc.SQLServerException

Cannot open database "<database name>" requested by the login. The login failed.

The database is invalid.

Check Database name of the connection resource.

com.microsoft.sqlserver.jdbc.SQLServerException

TCP/IP connection to the host <host name>, port 1433 failed.

Can't connect to the database.

Check Host name of the connection resource, or check the network.

com.microsoft.sqlserver.jdbc.SQLServerException

TCP/IP connection to host <server name>.database.windows.net, port 1433 failed. Error: "connect timed out. Open the connection properties and check that a SQL Server instance is running in the host, that TCP/IP connection to the port is permitted, and that the TCP connection to the port is not blocked by firewall."

The database name or the user name is invalid.

Check Database name or User name of the connection resource. Also, check whether the user name is in the format of "<user name>@<server name>".

com.microsoft.sqlserver.jdbc.SQLServerException

Incorrect syntax near '<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.

com.microsoft.sqlserver.jdbc.SQLServerException

Invalid object name '<table name>'

The table name is invalid.

Check Table name.

com.microsoft.sqlserver.jdbc.SQLServerException

Connection reset

The user name is invalid.

Check whether User name of the connection resource is in the format of "<user name>@<server name>".

com.microsoft.sqlserver.jdbc.SQLServerException

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 (username@servername). In addition, if both formats are used, the server names must match.

The user name is invalid.

Check whether User name of the connection resource is in the format of "<user name>@<server name>". Also, check whether the correct value is set in <server name>.

com.microsoft.sqlserver.jdbc.SQLServerException

Login failed for user '<user name>'

The user name or the password is incorrect.

Check User name or Password of the connection resource. Also, check whether the user name is in the format of "<user name>@<server name>".

InputDataNotFoundException

Input data isn't specified.

Specify Input data or draw data flow.

InvalidPropertyConfigurationException

SQL statement isn't set.

Specify SQL statement.

InvalidPropertyConfigurationException

Target column is not selected.

Target for Schema definition isn't selected in the Write Table operation.

Select one or more Target for Schema definition.

InvalidPropertyConfigurationException

Target column is not selected.

Target for Schema definition isn't selected in the Read Table operation.

Select one or more Target for Schema definition.

InvalidPropertyConfigurationException

Table name isn't set.

Specify Table name.

InvalidPropertyConfigurationException

Procedure isn't set.

Specify Procedure.

java.sql.SQLException

A database access error or some other one has occurred.

Check the SQLException message. SQLException message is based on the specifications of the driver. The cause of the error might be output in SQLException message.

For details on messages, contact the database vendor.

ResourceNotFoundException

Resource definition could not be found. Name: []

Destination isn't specified.

Specify Destination.

ResourceNotFoundException

Resource definition could not be found. Name: [<connection resource name>]

The resource definition selected in Destination isn't found.

Check the connection resource specified in Destination.

com.microsoft.sqlserver.jdbc.SQLServerException

Login failed for user '<user name>'

The user name or the password is incorrect.

Check User name or Password of the connection resource. Also, check whether the user name is in the format of "<user name>@<server name>".

TCP/IP connection to host <server name>.database.windows.net, port 1433 failed. Error: "connect timed out. Open the connection properties and check that a SQL Server instance is running in the host, that TCP/IP connection to the port is permitted, and that the TCP connection to the port is not blocked by firewall."

The database name or the user name is invalid.

Check Database name or User name of the connection resource. Also, check whether the user name is in the format of "<user name>@<server name>".

Connection reset

The user name is invalid.

Check whether User name of the connection resource is in the format of "<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 (username@servername). In addition, if both formats are used, the server names must match.

The user name is invalid.

Check whether User name of the connection resource is in the format of "<user name>@<server name>". Also, check whether the correct value is set in <server name>.

TCP/IP connection to the host <host name>, port 1433 failed.

Can't connect to the database.

Check Host name of the connection resource, or check the network.

Cannot open database "<database name>" requested by the login. The login failed.

The database is invalid.

Check Database name of the connection resource.

Invalid object name '<table name>'

The table name is invalid.

Check Table name.

Incorrect syntax near '<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.

 

Limitations of SQLAZURE category

 

Supported types

This connector supports the following types.

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

Limited

 

SQL_VARIANT

No

 

UNIQUEIDENTIFIER

No

 

  • Yes: Supported.

  • Limited: Supported with limitations.

  • No: Not supported.

 

Common to all operations

Specification limits

  • Databases with names that include the following characters can't be specified.

    = Remarks =

    For details, contact the database vendor.

    • "{"

    • ";"

  • When executing multiple operations of this connector in the same transaction, the connection may time out after 5 minutes due to the specification limits of Azure SQL Database.

Notes

  • SSL is used in communication between Azure SQL Database and this connector.

  • The establishment of connection may fail because of the reconfiguration of servers of Azure SQL Database. In this case, the reconnection is repeated for a certain period of time.

 

Read Table

Specification limits

  • Displaying table list

    • Tables that exist in schemas other than the dbo schema will be displayed as "<schema name>.<table name>".

  • The table name is case-insensitive even if it's enclosed with quotation marks.

 

Execute Select SQL

Specification limits

None.

Notes

  • A schema handled as byte[] type is output as binary format.

 

Write Table

Specification limits

  • Displaying table list

    • Tables that exist in schemas other than the dbo schema will be displayed as "<schema name>.<table name>".

  • DATETIME

    • When data is input in milliseconds, the millisecond values will be rounded. The values will be rounded to 0 milliseconds, 3 milliseconds, or 7 milliseconds, whichever is nearest.

      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)

    • When the data includes multi-byte characters, character corruption will occur.

  • The table name is case-insensitive even if it's enclosed with quotation marks.

 

Execute Update SQL

Specification limits

  • DATETIME

    • When data is input in milliseconds, the millisecond values will be rounded. The values will be rounded to 0 milliseconds, 3 milliseconds, or 7 milliseconds, whichever is nearest.

      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)

    • When the data includes multi-byte characters, character corruption will occur.

 

Execute Stored Procedure

Specification limits

  • DATETIME

    • When data is input in milliseconds, the millisecond values will be rounded. The values will be rounded to 0 milliseconds, 3 milliseconds, or 7 milliseconds, whichever is nearest.

      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)

    • When the data includes multi-byte characters, character corruption will occur.

  • XML

    • The operation can't be executed when XML type is included in the procedure arguments.

  • SQL_VARIANT

    • The operation can't be executed when SQL_VARIANT type is included in the procedure arguments.

  • UNIQUEIDENTIFIER

    • The operation can't be executed when UNIQUEIDENTIFIER type is included in the procedure arguments.

  • There are cases that a procedure with a name that has to be enclosed with quotation marks can't be used.

  • When a procedure to use output parameters is specified, the same parameters as the output parameters will be displayed in the input parameter settings, and input data will be required.

 

Policies     (c) Saison Technology Co.,Ltd. 2021

TOP