(SQL Server 2000, SP3a)
Hello all!
A while ago (2 years?) I downloaded a freeware auditing utility called SQLLog:
http://www.rlpsoftware.com/SQLLog.asp
It doesn't appear as if the freeware version is available from this site any more, so I
was hoping to solicit some opinions on a similar utility that would help audit database
deletions.
That old SQLLog utility basically put triggers on the desired tables, and squirted XML
into a blob field that would enumerate the fields and their original contents and any
changed data. It was pretty straightforward and simple to integrate with an existing
database.
If anyone knows of anything that might be applicable, I'd sure be grateful!
John PetersonI've used SQLAudit and it works well. It basically places triggers on the
tables for you.
SQLAudit
http://www.redmatrix.com/default.asp?section=sqlaudit
I've heard good reports on Lumigent Entegra, but I haven't evaluated that
yet - it's on my to-do list!
http://www.lumigent.com/products/entegra/entegra.htm
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:%23gxhuLLKEHA.2456@.TK2MSFTNGP12.phx.gbl...
> (SQL Server 2000, SP3a)
> Hello all!
> A while ago (2 years?) I downloaded a freeware auditing utility called
SQLLog:
> http://www.rlpsoftware.com/SQLLog.asp
> It doesn't appear as if the freeware version is available from this site
any more, so I
> was hoping to solicit some opinions on a similar utility that would help
audit database
> deletions.
> That old SQLLog utility basically put triggers on the desired tables, and
squirted XML
> into a blob field that would enumerate the fields and their original
contents and any
> changed data. It was pretty straightforward and simple to integrate with
an existing
> database.
> If anyone knows of anything that might be applicable, I'd sure be
grateful!
> John Peterson
>|||Thanks for the reply, Mark! I was checking out ApexSQL Log as well -- so this will be
nice to be able to compare/contrast. I see that Apex's solutions work by reading the
transaction log -- so no additional triggers need be in place. That seems like a pretty
clean solution.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:urpHFLQKEHA.1264@.TK2MSFTNGP12.phx.gbl...
> I've used SQLAudit and it works well. It basically places triggers on the
> tables for you.
> SQLAudit
> http://www.redmatrix.com/default.asp?section=sqlaudit
> I've heard good reports on Lumigent Entegra, but I haven't evaluated that
> yet - it's on my to-do list!
> http://www.lumigent.com/products/entegra/entegra.htm
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
>
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:%23gxhuLLKEHA.2456@.TK2MSFTNGP12.phx.gbl...
> > (SQL Server 2000, SP3a)
> >
> > Hello all!
> >
> > A while ago (2 years?) I downloaded a freeware auditing utility called
> SQLLog:
> >
> > http://www.rlpsoftware.com/SQLLog.asp
> >
> > It doesn't appear as if the freeware version is available from this site
> any more, so I
> > was hoping to solicit some opinions on a similar utility that would help
> audit database
> > deletions.
> >
> > That old SQLLog utility basically put triggers on the desired tables, and
> squirted XML
> > into a blob field that would enumerate the fields and their original
> contents and any
> > changed data. It was pretty straightforward and simple to integrate with
> an existing
> > database.
> >
> > If anyone knows of anything that might be applicable, I'd sure be
> grateful!
> >
> > John Peterson
> >
> >
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment