Re: sql tracing and logging



mc4u wrote:
The software I use came bundled with Informix and I would like to know
how to trace which tables the data is stored in from any given screen
in the application. For example, our support group informed me that
they ran a trace on the screen in question and they referenced only one
table. However, there are columns in this particular screen of the
application which do not belong to the table. Any suggestions on how to
trace or informix logging would be helpful.

Which version of IDS? Indeed, is the DBMS you're using IDS, or is it XPS or OnLine or SE? What language is the application written in? Platform?


Options to consider include:
* Dynamic SET EXPLAIN - requires IDS 9.40 or later.
* SQLIDEBUG - ideally requires sqliprint, which you may or may not have.
* I-Spy - requires an extra product and some configuration.
* Audit - ON-Audit, ON-ShowAudit; least informative, but would tell
  you which tables are in use.
* DB-Schema - would show you the database structure.  Add row counts
  (UPDATE STATISTICS) and you'd be able to track some activity.

There are probably other options too - network snooping is tantamount to using SQLIDEBUG without sqliprint, but would probably have less impact on the system, but only works for network connections.

--
Jonathan Leffler                   #include <disclaimer.h>
Email: jleffler@xxxxxxxxxxxxx, jleffler@xxxxxxxxxx
Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/
.



Relevant Pages

  • sql tracing and logging
    ... The software I use came bundled with Informix and I would like to know ... they ran a trace on the screen in question and they referenced only one ... trace or informix logging would be helpful. ... Prev by Date: ...
    (comp.databases.informix)
  • Re: Importing data from Informix to MSSQL2k5 fails
    ... Benedikt Ries wrote: ... Well, I for one don't see any trace of your problem information in this posting, so you can't get accurate help. ... It may also be said that those in the Informix camp are likely to be less sympathetic to your problem than those in the MS SQL Server 2005 camp. ...
    (comp.databases.informix)