Data Transformation Engine Database Interface Designer Reference Guide

Chapter 10 - Debugging and Viewing Results Database Trace Files
Database Interface Designer Reference Guide
161
Note A full database trace is most beneficial during map development; however, it is
preferable to use -TRACEERR in a production environment because only the
database errors are reported.
For example, if you generate the full database trace for a map called DBUpdate
that has three database input cards, it would produce the following 88-line
MultiDB’s.dbl file.
Database type is MS SQL Server
Status returned to engine: (0) Success
No existing connection was found.
Error in: dbopen
Error : 5701
State : 2
Message : Changed database context to 'master'.
Error in: dbuse
Error : 5701
State : 1
Message : Changed database context to 'pubs'.
A transaction was started.
Connection to SQL Server has been established.
Interface library version 6.0(140)
Data being retrieved for input card 1.
Database adapter version 6.0(140)
Starting a database unload...
Server\\Database: HP_NT\\pubs
Userid : sa
Password :
Query : SELECT * FROM Authors
Query size : 21
Output is to a buffer.
Statement execution succeeded.
The columns are of the following types:
Column 1 (au_id) type is varchar(11).
Column 2 (au_lname) type is varchar(40).
Column 3 (au_fname) type is varchar(20).
Column 4 (phone) type is char(12).
Column 5 (address) type is varchar(40).
Column 6 (city) type is varchar(20).
Column 7 (state) type is varchar(2).
Column 8 (zip) type is varchar(5).
Column 9 (contract) type is bit.
Number of buffers in fetch array = 1
Writing results to a buffer.
Retrieved 23 records (1810 bytes).
Status returned to engine: (0) Success
Database type is MS SQL Server
Status returned to engine: (0) Success
Interface library version 6.0(140)
Data being retrieved for input card 2.
Database adapter version 6.0(140)
Starting a database unload...
Server\\Database: HP_NT\\pubs
Userid : sa
Password :
Query : SELECT * FROM Publishers
Query size : 24