The Biggest Logging Anti-Pattern
Posted by Davy Brion on March 16th, 2010
The Inquisitive Coder – Davy Brion's Blog
Trying to walk that thin line between intelligence and ignorance
Meta
Subscribe
-
-
Recent Posts
- Hey, It Is MY Personal Time After All
- Estimates Are A Double-Edged Sword
- Is That How You Talk To People?
- The MVVM Pattern Is Highly Overrated
- Which Language Do You Code In?
- Using The Dynamic Keyword To Avoid Difficulties With Generics
- I Finally Caved: I’m On Twitter
- What’s Wrong With This Picture?
- 500 Posts
- Resharper 5.1’s Test Runner Is Broken
- Off For A Week
- Check Out QuickGenerate
- Working Overtime: What It Really Means
- More On System.Tuple And Serialization/Deserialization
- My First Request For The Next .NET Version
- MSDTC And Microsoft Security Essentials: A Killer Combo!
- Using Agatha’s Server-Side Caching
- Why Do We Recycle Our Application Pools?
- If You Can’t Say Something Bad About It, You Don’t Know It Well Enough
- Isolation At Work: Good Or Bad?
March 16th, 2010 at 4:04 pm
Judging by the file path, isn’t this a transaction log rather than a debug log? You would find something similar to this in your SQL Server data files.
March 16th, 2010 at 4:08 pm
The log file is encrypted and the format is not publicly available. The files are just used by DTS to manage transactions and aren’t really meant for viewing outside of what the service itself reads and uses.
March 16th, 2010 at 4:10 pm
@Mario
that’s certainly possible, though that file really isn’t very big on my machine
that path also has a Trace folder which contains more (even smaller) logfiles… they’re all binary as well
it’s just frustrating to see that when you are hoping for something that could help you debug an issue
March 16th, 2010 at 10:33 pm
This could actually just be the start of your problems, as I have translated the log file file, which reads, “all work and no play makes Jack a dull boy”.