Data Transformation Engine Database Interface Designer Reference Guide

Chapter 5 - Database Sources and Targets Database Connections and Transactions

Database Interface Designer Reference Guide

When connection sharing occurs between cards and maps within a map, the

connection is described as active as long as there are one or more cards or rules

that access a database and that have yet to be committed or rolled back. (For

example, an active transaction exists.) When there are no such cards or rules, the

connection is inactive, yet still alive.

Note When using a DBLOOKUP, DBQUERY, GET or PUT function, the Transaction >

Scope setting defaults to Map when the map SourceRule > FetchAs setting is

set to Integral. The Transaction > Scope setting will change to Burst when the

map SourceRule > FetchAs setting is set to Burst; the Transaction >

OnFailure setting is always Rollback.

Connection Factors

The factors determining whether a connection is reused are the following:

♦ the database type

♦ the connection string (if applicable), datasource, or database name

♦ the user ID

♦ the OnFailure setting (Commit or Rollback)

♦ the Transaction > Scope setting

♦ the SourceRule > FetchAs setting

♦ whether

-CCARD or -CSTMT are specified within the adapter’s command

Also, whether a connection will be part of a global transaction is determined by

the usage of the Global Transaction (

-GTX) adapter command in the Command

setting.