February 16, 2004 at 6:44 am
Does anyone know of a program that will read the Transaction log file for a database so that we can review what updates were done? (we are trying to resolve a problem and do not know where it is coming from).
February 17, 2004 at 2:16 am
February 17, 2004 at 4:40 am
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
February 17, 2004 at 7:19 am
Can you not run a SQL profiler trace with appropriate options to capture this information?
February 18, 2004 at 8:23 am
I believed LOG Explorer is the one you need. It read the transaction log backup you created
February 18, 2004 at 9:16 am
ApexSQL Log also works very nicely for this.
Francis
February 18, 2004 at 9:24 am
Not sure what exactly you are looking for. Are you looking for who or what caused the updates? If so, I don't believe the tools mentioned above will tell you who/what made the changes.
If your just looking for when the changes were made then maybe you could restore the database somewhere else and then the transaction log in increments of time slices.
"Keep Your Stick On the Ice" ..Red Green
February 18, 2004 at 11:57 am
As another said, ApexSQL log can do this for the most part. Might be better to have a sql trace, though, using Profiler or the trace stored procedures if it's on-going.
K. Brian Kelley
@kbriankelley
February 18, 2004 at 2:36 pm
I use Log Explorer, but for a quick, cheap look into a T-log, try the undocumented DBCC LOG.
Syntax:
DBCC log ({dbid|dbname}, [, type={-1|0|1|2|3|4}])
where:
dbid or dbname - Enter either the dbid or the name of the database
type - is the type of output, and includes these options:
0 - minimum information (operation, context, transaction id)
1 - more information (plus flags, tags, row length, description)
2 - very detailed information (plus object name, index name, page id, slot id)
3 - full information about each operation
4 - full information about each operation plus hexadecimal dump of the current transaction log's row.
-1 - full information about each operation plus hexadecimal dump of the current transaction log's row, plus Checkpoint Begin, DB Version, Max XDESID
by default, type = 0
Greg
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply