How to audit the operation from dbaccess or isql
Posted in 2007
Topics: Performance & Tuning, Server Administration, Security, Permissions & Auditing, Triggers, Constraints & Referential Integrity
Hi,
A bank customer want to audit the operation from dbaccess or isql? They don't
want to define triggers on those tables, because triggers will heat ids
performance. Do anybody has any suggestion ? thanks...
Some information is stored in the systables and sysmaster database. I
would write like a snooper program that scan's these information and log
what is needed.
David Reed
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
CHUAN LU
Sent: 18 July 2007 11:30 AM
To: ids@iiug.org
Subject: How to audit the operation from dbaccess or isql [9569]
Hi,
A bank customer want to audit the operation from dbaccess or isql? They
don't
want to define triggers on those tables, because triggers will heat ids
performance. Do anybody has any suggestion ? thanks...
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
Talk to IBM about iSpy and about the new features in IDS 11 (Cheetah) that were
added to the Secure Audit option.
Art S. Kagel
----- Original Message -----
From: Chuan Lu <ids@iiug.org>
At: 7/18 5:29:50
Hi,
A bank customer want to audit the operation from dbaccess or isql? They don't
want to define triggers on those tables, because triggers will heat ids
performance. Do anybody has any suggestion ? thanks...
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
But the custer's system is a product system, It's impossible for them to upgrade to IDS 11 or using i-spy. I have suggested them to check the columns of syssessions and syssqlcurses. If anybody still has good suggestion. Please told me. thanks...
They can certainly write a monitor that looks for new sessions in syssessions
and tracks down the pid/host/user combination to determine who is running
dbaccess/isql and from there to see what SQL they are running. However, such
queries are intrusive, hurting performance, if run too frequently and if they
are not run frequently enough then much is missed. That's why IDS 11 has new
built-in monitoring and data gathering/triggering features and enhanced audit
facilities. FWIW.
Art S. Kagel
----- Original Message -----
From: Chuan Lu <ids@iiug.org>
At: 7/18 23:13:52
But the custer's system is a product system, It's impossible for them to
upgrade to IDS 11 or using i-spy. I have suggested them to check the columns
of syssessions and syssqlcurses. If anybody still has good suggestion. Please
told me. thanks...
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.