From: | "Philippe Lang" <philippe(dot)lang(at)attiksystem(dot)ch> |
---|---|
To: | "Pgsql-Odbc (E-Mail)" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Sniffer to trace ODBC calls? |
Date: | 2003-12-09 18:03:18 |
Message-ID: | 6C0CF58A187DA5479245E0830AF84F420AF913@poweredge.attiksystem.ch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Hello,
What I'm interested in, is the actual data that is returned by the server, and as you mention, it is not traced by this tool.
I'm opening Access forms with a filter, and I'd like to know where the filtering is actually taking place: on the server, or on the client? I have a low-bandwith connection between the client and the server, this is something I have to take care of.
Thanks
Philippe
-----Message d'origine-----
De : Benjamin Riefenstahl [mailto:Benjamin(dot)Riefenstahl(at)epost(dot)de]
Envoyé : mardi, 9. décembre 2003 18:42
À : Philippe Lang
Cc : Pgsql-Odbc (E-Mail)
Objet : Re: [ODBC] Sniffer to trace ODBC calls?
Hi Philippe,
"Philippe Lang" <philippe(dot)lang(at)attiksystem(dot)ch> writes:
> Is there, for Windows or Unix, an ODBC "sniffer", that would allow
> to look at the queries and results that got through a network?
> Something like tcpdump or ethereal, but that shows ODBC calls and
> results more clearly.
Windows: See the "Tracing" tab in the "ODBC Data Source
Administrator". I think the trace only logs the queries and error
codes, not the actual data, but that should be enough usually.
benny
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Riefenstahl | 2003-12-09 18:36:07 | Re: Sniffer to trace ODBC calls? |
Previous Message | Benjamin Riefenstahl | 2003-12-09 17:41:38 | Re: Sniffer to trace ODBC calls? |