Capturing a trace of queries

Does anyone know how I can tell Informix to save into a log file the queries which it receives? -- Posted via Talkway - http://www.talkway.com Exchange ideas on practically anything (tm).

The Database and Service Level Monitor with ZERO impact wins! ============================================================ Tired of database monitors that do NOT measure end-user service levels and SQL performance in production? (they monitor only high level resources) Tired of database monitors that do NOT capture or monitor what causes 80% of all database server performance problems? (i.e. the end-user SQL transactions) Tired of database monitors that are intrusive, difficult to install, require thousands of dollars in consulting fees to setup, have a high cost of operation and are expensive? Tired of database monitors that are so intrusive they are not used 24x7 in production environments? Then you need the industry break-thru Zero Impact Sql and Service Level Monitors products from Sql Power Tools! Product Overview ================ The product line non-intrusively analyzes the SQL network packet flow to the database server for end-user SQL and service level performance monitoring. The product does NOT have to run on the database server, NOR on client workstations connected to the server. The products require NO intrusive database server monitors, agents, probes, audits, middleware or proxy servers. NO agents are installed on end user workstations. The products require NO impact upon the database servers, network or end-users. The products require no connections to the database server and end-users connect directly to the database server (not the monitor). Product installation is a three step process that can be completed in a few minutes. Product Line ============ Two products for database monitoring at the end-user SQL level: 1. 'Zero Impact Service Level Monitor' for 24x7 end-user and database server Service Level Monitoring with alerts. 2. 'Zero Impact Sql Monitor' for ZERO impact end-user SQL capture, performance monitoring, SQL transaction reconstruction and alert notification. Comparison to conventional database monitors ============================================ Conventional database monitoring products monitor at a very high level major resource usage such as cpu, memory, disk space, etc. They do NOT capture or monitor at the SQL transaction level, where 80% of all database server performance problems occur. Why you ask? Because the monitoring of operating system or database server cpu, memory, disk space, or other metrics is EASY! To monitor with ZERO impact at the end-user SQL transaction level is difficult (however allows immediate identification of unacceptable end-user service levels and poor performing SQL). The real business payoff with database monitoring products is obtained when monitoring occurs at the end-user SQL transaction level, not when monitoring high level system resources. Then the cause of production database server performance problems can be immediately pinpointed to specific SQL transactions. Benefits of the Zero Impact Sql Monitor and Zero Impact Service Level Monitor ======================================= Finally a database monitoring product is now available that performs what DBAs have always wanted and needed: 1. End-user service level monitoring with alert notification now possible with ZERO impact upon the database server and end-users. 2. SQL capture, performance monitoring and alert notification now possible with ZERO impact upon the database server and end-users. 3. Pinpoints the exact SQL or SQL transaction mix causing poor performance. Reconstruction of a service level or end-user SQL is possible by several criteria. 4. Trending database service level or SQL performance can be immediately detected at the SQL transaction level. 5. Requires NO intrusive database server monitors, agents, probes, audits, middleware or proxy servers. NO agents are installed on end user workstations. 6. Scales to thousands of users with no required impact upon the database server. 7. Time for resolution of database performance issues is dramatically reduced. Makes DBAs, System Administrators and Developers more productive. 8. Product installation is a few minutes. Ongoing cost of ownership is minimal. info@sqlpower.com www.sqlpower.com Sql Power Tools The Development Group for Advanced Technology, Inc. 201.825.9511 kik wrote in message ... >Does anyone know how I can tell Informix to save into a log file >the queries which it receives? >-- >Posted via Talkway - http://www.talkway.com >Exchange ideas on practically anything (tm). >

kik wrote: > Does anyone know how I can tell Informix to save into a log file > the queries which it receives? If you're on a civilized system (Unix or variants), and you're using a sufficiently civilized server (OnLine, IDS, etc) and a sufficiently recent version of ESQL/C (primarily CSDK 2.x), then you can set the SQLIDEBUG environment variable to a value such as 2:/tmp/sqli.out and the application will log all the data sent back and forth. You can then decipher the data with the sqliprint program. The actual data file will have an underscore and a process id after what you specified in SQLIDEBUG. The SQLIDEBUG environment variable has worked for quite some time (6.00?), but getting hold of sqliprint has been harder until it was distributed with CSDK. You can also use a value 1:/tmp/sqli.out to get some sort of ASCII dump, but it isn't as useful as the binary dump (IIRC; I've not used it more than once). This is not the same as what you asked for; you want a global monitor. If you're willing to risk the ire of the c.d.i community, and if you use network connections, you can consider R Reiter's over-advertized product. I'm not sure whether it completely addresses your problems. It certainly doesn't catch non-network information -- it is a glorified network packet sniffer. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN #include <disclaimer.h>