January 4, 2005 at 7:56 am
Now I thought this wouldn't be so difficult or require a thousand dollar add-in. How does one read a transaction log?
Why you ask? Well it seems we have over 50,000 records updated with no trail of who, what, when or where otherwise. We want know why to stop this terrible inconvenience of restore to back ups.
Thanks in advance,
Jolyn
January 4, 2005 at 12:54 pm
The thousand dollar add-in is Lumigent Log Explorer (actually, I don't know the price). http://www.lumigent.com
When I think of a log, I think of a file that I can look at as a history of what has happened. Unfortunately, that's not what the transaction log is. Its really more of a transaction facilitator than a log. But, Lumigent does have Log Explorer that will allow you to look at the log, and, I believe, selectively reverse transactions, assuming that your database is set to full recovery! If it is simple recovery, all bets are off. The transactions are not retained. Also, I think you have to already have Log Explorer installed when the transaction takes place in order to see it. I don't think you can install it today, and see transactions that happened yesterday.
Steve
January 4, 2005 at 5:42 pm
Actually Steve, Log Explorer can read transactions that were committed to t-logs before Log explorer was installed. It can even read log backup files.
Jolyn, you could try using DBCC LOG to read your t-log. It's pretty crude, but you might be able to decypher the data. There's an article about it here: http://www.mssqlcity.com/Articles/Undoc/SQL2000UndocDBCC.htm
Greg
Greg
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply