Messages and limitations of the SQL Server connector
Message code list of SQLSERVER category
The following message codes correspond to errors that occur in SQL Server Connector.
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
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:
|
Corresponding error
-
java.sql.SQLException
-
com.microsoft.sqlserver.jdbc.SQLServerException
Exception messages of SQLSERVER category
|
Exception name |
Cause |
Solution |
|
|---|---|---|---|
|
InputDataNotFoundException |
Input data isn't specified. |
Specify Input data or draw data flow. |
|
|
InvalidPropertyConfigurationException <Property name> is not specified. |
<Property name> isn't specified. |
Specify <property name>. |
|
|
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. |
|
|
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. |
|
Cannot open database "<database name>" requested by the login. The login failed. |
The database is invalid. |
Check Database name of the connection resource. |
|
|
The TCP/IP connection to the host <host name>, port <port number> has failed. |
Can't connect to the database. |
Check Host name of the connection resource, or check the network. |
|
|
Invalid object name '<table name>'. |
The table doesn't exist. |
Specify an existing table in 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 SQLSERVER category
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 |
Limited |
|
|
DATE |
Yes |
|
|
SMALLDATETIME |
Yes |
|
|
DATETIME |
Limited |
|
|
DATETIME2 |
Limited |
|
|
DATETIMEOFFSET |
Limited |
Data is handled as String. |
|
CHAR |
Yes |
|
|
VARCHAR |
Yes |
|
|
NCHAR |
Yes |
|
|
NVARCHAR |
Yes |
|
|
TEXT |
Yes |
|
|
NTEXT |
Yes |
|
|
BINARY |
Limited |
|
|
VARBINARY |
Limited |
|
|
IMAGE |
Yes |
|
|
VARCHAR(MAX) |
Yes |
|
|
NVARCHAR(MAX) |
Yes |
|
|
VARBINARY(MAX) |
Limited |
|
|
XML |
Limited |
|
|
SQL_VARIANT |
No |
|
|
UNIQUEIDENTIFIER |
No |
|
-
Yes: Supported.
-
Limited: Supported with limitations.
-
No: Not supported.
For more details on the specifications of database, such as rounding off and value range of each type, refer to SQL Server 2019 documents.
Specification limits
-
You can't connect to a database whose name includes the following characters. Some other characters may also disable connection to the database if they are included in the database name.
= Remarks =Data will be sent as Unicode.
For details, contact the database vendor.
Character
-
%
&
(
)
=
[
]
{
}
'
^
;
Specification limits
-
Displaying table list
-
Tables that exist in schemas other than the dbo schema will be displayed as "<schema name>.<table name>".
-
-
TIME
-
This can be retrieved to the millisecond.
-
-
DATETIME2
-
This can be retrieved to the millisecond.
-
-
The table name is case-insensitive even if it's enclosed with quotation marks.
Specification limits
-
TIME
-
This can be retrieved to the millisecond.
-
-
DATETIME
-
If you're substituting the value of DATETIME type available to the millisecond using SQL parameter for WHERE clause, it can't be accurately determined by the comparison operator.
However, this can be avoided by converting the value into string format "yyyy-MM-dd HH:mm:ss.SSS" with Mapper and changing the type of SQL parameter to VARCHAR type.
-
-
DATETIME2
-
This can be retrieved to the millisecond.
-
Specification limits
-
Displaying table list
-
Tables that exist in schemas other than the dbo schema will be displayed as "<schema name>.<table name>".
-
-
TIME
-
This can be specified to the millisecond.
-
-
DATETIME2
-
This can be specified to the millisecond.
-
-
The table name is case-insensitive even if it's enclosed with quotation marks.
Specification limits
-
TIME
-
When using SQL Parameter, it can be specified to the millisecond.
-
-
DATETIME
-
If you're substituting the value of DATETIME type available to the millisecond using SQL parameter for WHERE clause, it can't be accurately determined by the comparison operator.
However, this can be avoided by converting the value into string format "yyyy-MM-dd HH:mm:ss.SSS" with Mapper and changing the type of SQL parameter to VARCHAR type.
-
-
DATETIME2
-
When using SQL Parameter, it can be specified to the millisecond.
-
Specification limits
-
TIME
-
Input parameters can be specified to the millisecond.
-
Output parameters can be retrieved to the millisecond.
-
-
DATETIME2
-
Input parameters can be specified to the millisecond.
-
Output parameters can be retrieved to the millisecond.
-
-
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.
Specification Limits
-
Tables which include "." in the schema name or the table name on the database can't be used.
-
Test execution may be failed if the data amount is huge.
-
The maximum record count shown in the Execution result tab is 100.
-
SQL statements can be re-edited only if the tables in the SQL statement exist.
Specification Limits
-
When the connection resource is XAResource, testing can't be executed.
-
Tables which include "." in the schema name or the table name on the database can't be used.
-
SQL statements can be re-edited only if the tables in the SQL statement exist.
-
In connection resources for JDBC connector, when Execute transaction processing is not selected, rollback is not performed in test execution, and the data is updated.