jdbc-query tracing/logging
- From: "eteunisse" <eteunisse@xxxxxxxxx>
- Date: 15 Jul 2005 04:45:38 -0700
There are a lot of solutions given in this group but I think they are
not exactly what I need/want.
I have a Linuxserver (Ingres 2.6). A remote client can query the
databases on this server through a JDBC-connection.
This client is a complete blackbox. I only know that it can shoot
queries. I do not have any idea what kind of queries.
Now they want me to limit the output so that the client can't select
the whole 3,5 GB dataset.
The problem is offcourse that I first have to know what kind of queries
the client is going to shoot at my databases before I can decide if a
limit has to be set at all. And if a limit has to be set I want to be
able to decide what kind of limit I have to set.
The JDBC-connection is only possible through one user.
What is the best way to trace al the queries this client shoots at the
server?
printqry and use a pipe to redirect all the sessions to one file?
(where do I have to set up the pipe? In the .bashrc from the user the
JDBC-connection uses? I'm used to VMS, so Linux is a bit new)
use some kind of audting?
Thanks for any advice!
Erwin
.
- Follow-Ups:
- Re: jdbc-query tracing/logging
- From: Roy Hann
- Re: [Info-ingres] jdbc-query tracing/logging
- From: martin . bowes
- Re: jdbc-query tracing/logging
- Prev by Date: Re: Sysmod sql
- Next by Date: RE: Calling Ingres Database Procedures through .Net Data Provider
- Previous by thread: [Info-ingres] Fwd: Senior Analyst Programmer - Melbourne
- Next by thread: Re: [Info-ingres] jdbc-query tracing/logging
- Index(es):
Relevant Pages
|