This is a multi-part message in MIME format.

------_=_NextPart_001_01C0B2E2.9A97D908
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Typically I do this all from within triggers of the tables themselves.
You can use triggers to trap the events and take whatever action is
appropriate.

 -----Original Message-----
From: 	francoisvdw@w...
[mailto:francoisvdw@w...]
Sent:	Wednesday, March 21, 2001 11:44 PM
To:	sql language
Subject:	[sql_language] Profiler - Audit trail, Yelp!

Hi

We are developing an online secure loan system between banks. All
actions
on the database (and front-end) must be logged and stored for auditing
purposes. Profiler will do the trick (unless any of you have other
suggestions) but we need 24 hrs uptime. Is there any way in SQL itself
to
prevent someone from stopping the service (iow disabling the audit
trail)
Seeing that profiler is a trace/audit tool there must be a
setting/code/registry/dll or something we can configure to prevent
accidental or malicious stopping of the profiler trace

Thx guys

Francois van der Walt
Senior database analyst
Southern Focus Consulting (Pty)Ltd
francoisv@s...
+xxxx xxx xxxx
$subst('Email.Unsub')