Re: Transaction Log
From: Erland Sommarskog (sommar@algonet.se)
Date: 07/27/02
- Next message: ray: "Re: Column level security"
- Previous message: Erland Sommarskog: "Re: Tracking Stored Procedure changes"
- In reply to: Andrew J. Kelly: "Re: Transaction Log"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Erland Sommarskog <sommar@algonet.se> Date: Sat, 27 Jul 2002 21:52:06 +0000 (UTC)
Andrew J. Kelly (akelly@targitinteractive.com) writes:
> Yes that is correct. The tool from Lumigent is the only one I know of
> that uses the log in this fashion. He was looking for some way to track
> changes. The logs are usually truncated or not necessarily kept for that
> long of a period so if you what a history of who did what and when,
> triggers is generally the way to do it.
As I understand it, Log Explorer can read from backups too. Of course,
it could be quite tedious of getting through all backups for a month.
Then again, triggers could have quite an impact on performance.
Perhaps it would be an idea for someone to use Log Explorer to read
a transaction log dump and then update the auditing tables? This way
you could business run as usual during the day, and then during
the night - or in a background process - update the audit tables?
-- Erland Sommarskog, SQL Server MVP sommar@algonet.se Books Online (updated!) for SQL 2000 at http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
- Next message: ray: "Re: Column level security"
- Previous message: Erland Sommarskog: "Re: Tracking Stored Procedure changes"
- In reply to: Andrew J. Kelly: "Re: Transaction Log"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
