sql tracing and logging

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

mc4u - 28 Oct 2005 17:57 GMT

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.
Thanks

Reply to this Message

Jonathan Leffler - 29 Oct 2005 07:14 GMT

> 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
[quoted text clipped - 3 lines]
> 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.

Signature

Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/

Reply to this Message

Konikoff, Rob (Contractor) - 31 Oct 2005 15:34 GMT

MC4U:

One of the things I have done in the past with multiple tables is to
create a VIEW with linked tables into a single reference. It makes ad
hoc PERFORMs a snap. If the support group was looking as a specific
form, you may want to look at the underlying code for it.

Of course, I'm in an ancient version of IDS (7.2x).

Rob

-----Original Message-----
From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org]
On Behalf Of Jonathan Leffler
Sent: Saturday, October 29, 2005 2:15 AM
To: informix-list@iiug.org
Subject: Re: sql tracing and logging

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.

Signature

Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/
sending to informix-list

Reply to this Message