Database Reference
In-Depth Information
test 1c4-186c EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 0x008B9808
SQLINTEGER 201 <SQL_ATTR_CONNECTION_POOLING>
SQLPOINTER 0 <SQL_CP_OFF>
SQLINTEGER -6
test 1c4-186c ENTER SQLAllocConnect
HENV 0x008B9808
HDBC * 0x004CAAB8
test 1c4-186c EXIT SQLAllocConnect with return code 0(SQL_SUCCESS)
HENV 0x008B9808
HDBC * 0x004CAAB8 ( 0x008BA108)
test 1c4-186c ENTER SQLGetInfoW
HDBC 0x008BA108
UWORD 10 <SQL_ODBC_VER>
PTR 0x004CAA84
SWORD 22
SWORD * 0x00000000
test 1c4-186c EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0x008BA108
UWORD 10 <SQL_ODBC_VER>
PTR 0x004CAA84 [ -3] "03.80.0000\ 0"
SWORD 22
SWORD * 0x00000000
As you can see, the function calls are logged as a pair of
Enter
and
Exit
blocks along with the return codes. You
can verify details like the connection pooling information and ODBC driver version from the trace. In the case of an
error, you will see an error block with a diagnosis (
DIAG
) code for further analysis as in the following snippet:
test 1c4-186c
EXIT SQLDriverConnectW with return code -1
(SQL_ERROR)
HDBC 0x008BA108
HWND 0x000F0598
WCHAR * 0x0F63B45C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x0F63B45C
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
DIAG [08001] Unable to establish connection with hive server (-1)
If the ODBC driver you use does not implement its own logging mechanism, this standard Windows ODBC trace
is the only option to check ODBC API calls and their return codes. You can also follow the step-by-step process in the
