2 3 8 Database Configuration

ID

An identifier to uniquely identify this Configuration. To make use of a database Configuration, you will specify this name as the value for the DBCONFIG parameter of the SQL_CONNECT activity or for the database connection parameter for a Transformation Map.

This should describe the Configuration.

Active or Inactive. Configurations cannot be used in a processing sequence while they are in inactive status – supplied activities will end in error if they attempt to use a configuration that has inactive status.

Specifies the JDBC connection string necessary to connect to the required database from the environment in which the Processing Sequence will run. The following is an example of a JDBC connection string:

Identifies the Java class name of the JDBC driver used with this connection. The following is an example class name for the driver commonly used to access IBM i databases.

If authentication is required, this contains the authentication user name.

If authentication is required, this contains the password which is used with the database user.

This indicates if information should be automatically committed to the database using auto-commit support in the driver and/or database server.  Depending on the particular database and driver, auto-commit in effect can make every SQL statement a transaction.  Note that this can effectively defeat transaction control implemented at the application layer, for example, if the Use Transactions option is checked in the mapping tool.

Commitment control can also be affected or controlled using options in the transformation map definition and in the JDBC connection string. You would usually only use this setting when transaction control has not been implemented in the transformation map definition. These considerations, however, can vary according to the database system and the JDBC database driver.

The level of transaction isolation to be applied to the database connection.

None No transaction isolation applies. All uncommitted data is readable from any connection.

Read uncommitted
All uncommitted data is readable from any connection. This is the same as not having any isolation (None).

Read committed
This prevents dirty reads but does not prevent phantoms or non-repeatable reads. Using this isolation level, only data committed before the current transaction began will be available. Any dirty data or changes made by concurrent transactions will not be available.

This level is obviously more restrictive than the Read uncommitted.

Repeatable read
This prevents dirty and non-repeatable reads but does not prevent phantom rows. This means the probability of other transactions having to wait for this one are increased when compared to Read uncommitted and Read committed

This is more restrictive than Read committed.

Serializable
Serializable provides the highest transaction isolation. When a transaction is isolated at the Serializable level, only data committed before the transaction began is available. Neither dirty data nor concurrent transaction changes committed during transaction execution are available. This level emulates serial transaction execution, as transactions will effectively be executed one after another rather than concurrently.