Auditing SQL Server?

Are there any suggestions for auditing transactions including 'selects'
without the use of 'triggers'? Triggers are something our client can NOT use.
TIA
REM>> Are there any suggestions for auditing transactions including 'selects'
>> without the use of 'triggers'?
Using profiler to trace the t-SQL statements might be feasible for auditing
SELECT statements, but in transaction heavy systems, this can be a potential
performance issue. Third party products like Entegra from Lumigent also has
a trace-based auditing provision for SELECT statements issued against a
database.
--
Anith|||YOu could
-pass everything though a stored produre to keep track of it.
-Query the logfile with a logfile application
-Run the profiler and let him trace the statements to a table. 8depending
onyour application this will cost mcuh disk space)
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"dt09359" <dt09359@.discussions.microsoft.com> schrieb im Newsbeitrag
news:79C5DC37-01A0-4502-8F26-3156B811F03C@.microsoft.com...
> Are there any suggestions for auditing transactions including 'selects'
> without the use of 'triggers'? Triggers are something our client can NOT
> use.
> TIA
> REM