data modification logging solution

Anyone has a data modification logging solution such that reverting back is
always an option should a need arises for 'undo-ing' a committed transaction
?
--
bicHi
LogPI http://www.logpi.com
Log Explorer http://www.lumigent.com/products/le_sql.html
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"bic" wrote:

> Anyone has a data modification logging solution such that reverting back i
s
> always an option should a need arises for 'undo-ing' a committed transacti
on?
> --
> bic|||Hi,
One solution is to audit the data via triggers . A simple approach (one
that uses lots of space) is to dupicate the existing table and add the
following columns
UserName
ChangedDate
ChangeType
Then create three (or one if you like) triggers which will copy the data
from the event in to the table from the trigger tables(Inseted and Deleted)
This approach does use a lot of space but you can get the rows back very
simply
kind regards
Greg O
Need to document your databases. Use the firs and still the best AGS SQL
Scribe
http://www.ag-software.com
"bic" <bic@.discussions.microsoft.com> wrote in message
news:FDB88507-3F35-4F09-9816-58D10E6D9165@.microsoft.com...
> Anyone has a data modification logging solution such that reverting back
> is
> always an option should a need arises for 'undo-ing' a committed
> transaction?
> --
> bic