You can use the ODBC Driver Manager Trace tool to trace a connection to any ODBC data source that you access in PowerBuilder through the ODBC interface.
Unlike the Database Trace tool, the ODBC Driver Manager Trace tool cannot trace connections through one of the native database interfaces.
ODBC Driver Manager Trace records information about ODBC API calls (such as SQLDriverConnect, SQLGetInfo, and SQLFetch) made by PowerBuilder while connected to an ODBC data source. It writes this information to a default log file named SQL.LOG or to a log file that you specify.
The information from ODBC Driver Manager Trace, like Database Trace, can help you:
Understand what PowerBuilder is doing internally while connected to an ODBC data source
Identify and resolve problems with your ODBC connection
Provide useful information to Technical Support if you call them for help with your database connection
Use ODBC Driver Manager Trace instead of the Database Trace tool if you want more detailed information about the ODBC API calls made by PowerBuilder.
Performance considerations
Turning on ODBC Driver Manager Trace can slow your performance
while working in PowerBuilder. Therefore, use ODBC Driver Manager
Trace for debugging purposes only and keep it turned off when you
are not debugging.
PowerBuilder writes ODBC Driver Manager Trace output to a default log file named SQL.LOG or to a log file that you specify. The default location of SQL.LOG is in your root directory.
