Re: tracing odbc errors

From: Rea Peleg (rea_p_at_afek.co.il)
Date: 06/07/04 

Date: Mon, 7 Jun 2004 15:44:13 +0200

Thanks alot Sue
I got the odbc manager tracing going.
I'd appriciate it if you can refer me to a source which explains how to
decode it..
Thanks again
Rea
"Sue Hoegemeier" <Sue_H@nomail.please> wrote in message
news:9sm8c0h7sjv9ihipubhie9qovp01gqaeml@4ax.com...
> 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
> >
>