ODBC sniffing...

From: RamG (xyz_at_abc.com)
Date: 02/28/04 

Date: Sat, 28 Feb 2004 22:27:23 +0530

Hi,
  I have a VC++ program (exe) through which I want to find out the SQL
statements (INSERT, UPDATE, DELETE, SELECT and any stored procedure calls
with parameter values) that are issued by another Client/Server executable
on a database. Both the exes will be running on the client machine while
the database exists on the server machine. Is there some way of finding
this information?

  Will the ODBC log file be of any use? Can it give info about the SQL
statements and the values passed to the queries. Is there any other way of
doing it without reading the log files?

- how to get the log file to be created on the client side
- will the log file have the complete SQL statement with values passed by
the exe
- is there a different method for sniffing the SQL statements issued on the
client side.

  Info about the above questions will be of great help.

  Please respond back on this group itself.

Thanks,
RamGopal

Relevant Pages

  • ODBC logging....
    ... I have a VC++ program (exe) through which I want to find out the SQL ... Both the exes will be running on the client machine while ... Will the ODBC log file be of any use? ...
    (microsoft.public.data.odbc)
  • Re: Dont understand what version of SQL to install
    ... I'm talking about developing and testing databases for my client and ... To my XP, I can add SQL Developer 2008 to develop (I guess I should say, ... So I can use SQL Developer 2008 to create a database in standard 2005, ... installed on Client OSs such as Windows Vista. ...
    (microsoft.public.sqlserver.setup)
  • Re: DataSet.GetChanges() in RowChanged(DataRowAction.Add)
    ... have you considered SQL Express and use ... > I realize now that I didn't describe well how the client application is ... > Framework installed on the client machine, but not any SQL Server). ... > 20 tables in different relations with eachother in the database, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Oracle 10g2 LIKE operator and case-insensitive issues
    ... SQL> CREATE INDEX IDXTESTCASE ON AUTENTI; ... Predicate Information: ... 338 bytes received via SQL*Net from client ... sorts (memory) ...
    (comp.databases.oracle.server)
  • Re: Oracle 10g2 LIKE operator and case-insensitive issues
    ... SQL> CREATE INDEX IDXTESTCASE ON AUTENTI; ... Predicate Information: ... 338 bytes received via SQL*Net from client ... sorts (memory) ...
    (comp.databases.oracle.server)
Loading