Re: tracing odbc errors

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 06/07/04 

Date: Mon, 07 Jun 2004 06:16:57 -0600

Open the ODBC Data Source Administrator (odbcad32.exe).
Select the tracing tab and click on the button Start Tracing
Now. This will start a generic ODBC trace using the log file
specified in the Log File Path on the Tracing tab of the
ODBC Data Source Administrator.
When you are done tracing, make sure to turn if off as it
will slow things down. To turn off the tracing, open the
ODBC Data Source Administrator, select the Tracing tab and
click on the Stop Tracing Now button.
You can review ODBC errors in the trace file.

-Sue

On Mon, 7 Jun 2004 09:17:30 +0200, "Rea Peleg"
<rea_p@afek.co.il> wrote:

>Hi all
>I need some guiding to best practices for tracing odbc errors.
>I'm using a propriatary odbc driver (for a tabula rdbms server) which i
>suspect does not pass some errors to sqlsserver (where i run a job which
>includes a connection
>using such driver).
>Are there any generic tracing methods which can help follow odbc massages
>out side of sql server logs?
>TIA
>Rea
>

Quantcast