Another approach is to insert a pass through proxy to log traffic on
port 3050, and then review the logs after a couple of weeks operation.
This imposes a small communications penalty, but if the proxy resides on
the same box as the server you should be able to limit the impact.

There would be a lot of garbage, but you should be able to write a
filter program to peel out only the SQL from the logs. After all, the
information is there for Firebird to peel outthe SQL from the rest of
the data stream.

On Thu, 2005-05-12 at 09:58 +0000, Svein Erling Tysvær wrote:
> --- In firebird-support@yahoogroups.com, "KIMURA, Meiji" wrote:
> > Hi All,
> > I want to trace SQL statements issued from the client
> > application, in order to omit (or optimize) redundant SQLs for
> > tuning. Is there any method to trace SQL statements (like a
> > V$SQL_TEXT in Oracle) ?
>
> Hi Meiji!
>
> I don't know of any way to see all the statements that are sent to the
> server - although I'm not certain this is because it does not exist;
> it may also be because of my lacking knowledge. Though if you use IBO,
> I do know it is possible to use a TIB_Monitor in your application to
> see the statements IBO issues within that application.
>
> HTH,
> Set
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>