August 14, 2003 at 10:34 am
I seem to recall a way to read the transaction log without spending thousands of $$$ for a third party tool. Can anyone help?
August 14, 2003 at 10:57 am
Lockwood Techs tool right now is in beta, I don't know how much they will charge when it goes gold. But you can't beat the price right now.
And it is excellent and they are very helpful
August 14, 2003 at 11:20 am
Lumigent is the other, does run around $1000 a copy. Works pretty well. Havent tried Lockwood tool yet, but both Lumigent and Lockwood have been advertising with us for a while, good to work with.
Andy
August 15, 2003 at 12:08 am
Hi gfahrlander,
quote:
I seem to recall a way to read the transaction log without spending thousands of $$$ for a third party tool. Can anyone help?
a limited information you can get by using an undocumented command
DBCC log ( {dbid|dbname}, [, type={0|1|2|3|4}] )
where dbid|dbname is quite clear and 0, 1, 2, 3, 4 is the degree of details you'll in return.
However, unless you don't do you tax declaration in hexadecimal, I would certainly spent some money for a third party tool. I think LogExplorer is also available as 30 days trial version, but I'm not sure
Cheers,
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
August 15, 2003 at 7:04 am
I've never been asked to read the transaction log, but I'm pretty much a novice at this DBA stuff!
What are some reasons why a DBA would do this, especially if you have to buy a third party tool?
August 15, 2003 at 7:11 am
Thanks to all who responded. Ahh yes the old undocumented DBCC LOG command. Why would I want to read the log? I can tell what was going on when my tran log grew from 30 MB to 17 GB in 20 minutes. Also, I can use it for point in time recovery.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply