I am pretty new to SQL Server, and have been given the task of designing a
pretty large ASP-based web application for an intranet.
It needs to have an audit trail on every field and every table to ensure
that any data modified, added, or deleted is tracked.
Can SQL Server do it's own auditing and if so how good is it, or should I
build in my own system using ASP?
ThanksYou should build in your own auditing... Probably by adding triggers to the
tables.
The only other thing you can do is read the transaction log with a tool made
by Lumingent ( www.lumigent.com) called LogExplorer...
But you should do your own, this will allow you to capture more information
than what is in the log ( like hostname)
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Keith" <@..> wrote in message news:ehMbMNyEEHA.3180@.TK2MSFTNGP12.phx.gbl...
> I am pretty new to SQL Server, and have been given the task of designing a
> pretty large ASP-based web application for an intranet.
> It needs to have an audit trail on every field and every table to ensure
> that any data modified, added, or deleted is tracked.
> Can SQL Server do it's own auditing and if so how good is it, or should I
> build in my own system using ASP?
> Thanks
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment