The value must be a string containing the name of a valid code page supported by your JVM, for example, If set to 1 (the default), the driver checks the data type being requested against the data type of the table column storing the data.If a conversion between the requested type and column type is not defined, the driver generates an "unsupported data conversion" exception regardless of the data type of the column value.For Microsoft SQL Server 2005, this includes triggers fired by Data Definition Language (DDL) events.
Sending String parameters as the type the database expects improves performance and prevents unexpected locking issues caused by data type mismatches.
property controls whether the driver sends String parameter values to the server as Unicode (for example, nvarchar) or non-Unicode (for example, varchar).
If set to SSL, the login request and data is encrypted using SSL.
If the database server does not support SSL, the connection fails and the driver throws an exception.
Although trigger results are ignored, any errors generated by the trigger are reported.
Any warnings generated by the trigger are enqueued.If set to 0, the driver does not perform the data type check if the value of the column is null.This allows null values to be returned even though a conversion between the requested type and the column type is undefined. Controls whether the driver attempts to determine, at execute time, how to send String parameters to the server based on the database data type.This property helps applications in which character columns are all Unicode or all non-Unicode.For applications that access both Unicode and non-Unicode columns, a data type mismatch still occurs for some columns if the driver always sends String parameter values to the server in only one format.If the driver cannot load the DLL, the driver throws an exception.