|
Property
|
Characteristic
|
|
Determines how the driver reports results that are generated by database triggers (procedures that are stored in the database and executed, or fired, when a table is modified).
The driver does not report trigger results if the statement is a single Insert, Update, Delete, Create, Alter, Drop, Grant, Revoke, or Deny statement.
In addition, the only result that is returned is the update count that is generated by the statement that was executed (if errors do not occur). Although trigger results are ignored, any errors that are generated by the trigger are reported. Any warnings that are generated by the trigger are enqueued. If errors are reported, the update count is not reported.
|
|
|
Specifies whether the driver connects to read-write databases or requests read-only routing to connect to read-only database replicas. Read-only routing only applies to connections in Microsoft SQL Server 2012 where AlwaysOn Availability Groups have been deployed.
By default, the driver connects to a read-write node in the AlwaysOn environment.
|
|
|
Determines which type of metadata information is included in result sets when an application calls DatabaseMetaData methods.
By default, result sets do not contain synonyms.
|
|
|
The code page to be used by the driver to convert Character data. The specified code page overrides the default database code page or column collation. All Character data returned from or written to the database is converted using the specified code page.
By default, the driver automatically determines which code page to use to convert Character data. Use this property only if you need to change the driver’s default behavior.
|
|
|
Specifies the name of the database or instance to which you want to connect.
|
|
|
Specifies one or multiple SQL commands to be executed by the driver after it has established the connection to the database and has performed all initialization for the connection. If the execution of a SQL command fails, the connection attempt also fails and the driver throws an exception indicating which SQL command or commands failed.
|
|
|
Determines the amount of memory used by the driver to cache insensitive result set data.
The default is 2048.
|
|
|
Determines whether the driver caches long data (images, pictures, long text, binary data, or XML data) in result sets. To improve performance, you can disable long data caching if your application retrieves columns in the order in which they are defined in the result set.
By default, the driver caches long data in result sets in memory with a memory buffer of 2048 KB for caching result set data. If the size of the result set data exceeds available memory, the driver pages the result set data to disk.
|
|
|
Determines the number of bytes for each database protocol packet that is transferred from the database server to the client machine (Microsoft SQL Server refers to this packet as a network packet).
Adjusting the packet size can improve performance. The optimal value depends on the typical size of data that is inserted, updated, or returned by the application and the environment in which it is running. Typically, larger packet sizes work better for large amounts of data. For example, if an application regularly returns character values that are 10,000 characters in length, using a value of 32 (16 KB) typically results in improved performance.
By default, the driver uses the maximum packet size that the database server accepts.
|
|
|
Determines whether the driver returns table name information in the ResultSet metadata for Select statements.
By default, the driver does not perform additional processing to determine the correct table name for each column in the result set when the ResultSetMetaData.getTableName() method is called. The getTableName() method may return an empty string for each column in the result set.
|
|
|
A hint to the driver that determines whether the driver requests a database cursor for Select statements. Performance and behavior of the driver are affected by this property, which is defined as a hint because the driver may not always be able to satisfy the requested method.
By default, the database server sends the complete result set in a single response to the driver when responding to a query. A server-side database cursor is not created if the requested result set type is a forward-only result set. Typically, responses are not cached by the driver. Using this method, the driver must process the entire response to a query before another query is submitted. If another query is submitted (using a different statement on the same connection, for example), the driver caches the response to the first query before submitting the second query. Typically, the direct method performs better than the cursor method.
|
|
|
Allows your application to use Snapshot Isolation for connections.
This property is useful for applications that have the Serializable isolation level set. Using the SnapshotSerializable property allows you to use Snapshot Isolation with no or minimum code changes. If you are developing a new application, you may find that using the constant TRANSACTION_SNAPSHOT is a better choice.
By default, the application uses the Serializable isolation level when your application has the transaction isolation level set to Serializable.
|
|
|
Enables DataDirect Spy to log detailed information about calls issued by the driver on behalf of the application. DataDirect Spy is not enabled by default.
|
|
|
Determines whether the driver suppresses "changed database" and "changed language" warnings when connecting to the database server.
By default, warnings are not suppressed.
|
|
|
Controls how the driver delimits the start of a local transaction.
By default, the driver uses implicit transaction mode. This means that the database, not the driver, automatically starts a transaction when a transactionable statement is executed. Typically, implicit transaction mode is more efficient than explicit transaction mode because the driver does not have to send commands to start a transaction and a transaction is not started until it is needed. When TRUNCATE TABLE statements are used with implicit transaction mode, the database may roll back the transaction if an error occurs. If this occurs, use the explicit value for this property.
|
|
|
Determines whether the driver truncates timestamp values to three fractional seconds. For example, a value of the datetime2 data type can have a maximum of seven fractional seconds.
By default, the driver truncates all timestamp values to three fractional seconds.
|
|
|
Determines whether the driver uses server-side cursors when an updatable result set is requested.
By default, the client-side updatable cursors are created when an updatable result set is requested.
|
|
|
The transaction group ID that identifies any distributed transactions that are initiated by the connection. This ID can be used for distributed transaction cleanup purposes.
You can use the XAResource.recover method to roll back any transactions left in an unprepared state. When you call XAResource.recover, any unprepared transactions that match the ID on the connection used to call XAResource.recover are rolled back.
|