Re: Audit a Table

From: Paul Ibison (Paul.Ibison_at_Pygmalion.Com)
Date: 05/01/04 

Date: Fri, 30 Apr 2004 23:47:41 +0100

Matt,
you could create triggers which write these details to an audit table if you
want to do this continuously, or as a temporary measure you could run a tool
called Profiler and monitor the TSQL and Stored Procedure events.
Regards,
Paul Ibison

Relevant Pages

  • Re: Audit logging an adp
    ... Allen Browne's audit code. ... Some people may be tempted to suggest using SQL Server triggers, ... but without an adequate security model your audit trail ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Audit logging an adp
    ... if Access MDB had triggers; I would probably be using it right now lol. ... Allen Browne's audit code. ... Some people may be tempted to suggest using SQL Server triggers, ... but without an adequate security model your audit trail ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Tracking object state for auditing
    ... the puprose of "tracking" would be to ultimately "audit" the changes ... creating triggers and the like is not ... something the "powers that be" will allow. ... > A very very simple way to track changes to data in a database is to ...
    (comp.object)
  • Re: Results of Altering Trigger NOT FOR REPLICATION
    ... audit tables and they are therefore being kept in synch that way. ... altered the triggers so that they are NOT FOR REPLICATION. ... > the trigger to NFR and replicate both tables. ...
    (microsoft.public.sqlserver.replication)
  • Re: How to know which tables is updated ?
    ... You could use profiler to audit certain types of activity & subsequently see what activity has occured through time. ... You could use triggers &/or default values to maintain a list of who & when records are added. ... is there any utility in Sql Server 2000 or any kind of third party tool available? ...
    (microsoft.public.sqlserver.server)