Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
JohnDeere
Posting Yak Master
191 Posts |
 Posted - 2004-02-10 : 19:26:26
|
| I recently started getting incorrect transaction log usage reported by EM, dbcc sqlperf (logspace) and any other monitoring tool. I have seen this in pre 7.0 versions but I had never seen since it since. I spent 8 hours on the phone with Microsoft and they finally guessed that the it is a bug in the calculation based on the fact that our active virtual log is somewhere in the middle of the transaction log file. They pointed me to KBA281879 which refers to a problem in SQL 7.0 and dbcc sqlperf (logspace). What is really frustrating is that they have no reliable fix. Maybe shrinking the log file, maybe switch from full to simple recovery mode and back again or just live with it. It is hard to setup threshold monitoring when your log is only using 20MB but all the monitors are reporting 150MB space used. Does anyone have any experience with this problem?ThanksLance Harra |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2004-02-10 : 20:52:08
|
I've seen this behavior for so long I've forgotten when I stopped considering it a bug.  In addition to switching recovery modes and shrinking, you can also try adding a new, separate log file and dropping the old one. That lets you start with a clean file, and depending on how often you have the problem you may even want to make a regular maintenance plan to do this.To be honest though, I wouldn't worry too much about it as long as the log is sized big enough to allow for the biggest transaction you'll get. With regular log backups it will eventually even out and report accurately. Worst case, just increase the size of the log...unless it's already at 1GB or higher. |
 |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2004-02-10 : 21:01:01
|
quote:
I've seen this behavior for so long I've forgotten when I stopped considering it a bug.
Memo To : Ballmer, SteveSubject : Operative #8362823Message : The transformation is complete.Damian |
|
|
|
JohnDeere
Posting Yak Master
191 Posts |
Posted - 2004-02-10 : 22:55:18
|
| I guess I will just live with it. Since this is a 24x7 system. The log file is currently a little over 3GB due to the way the database was initially loaded via a vb application that synchronizes data between this database and our RDB database running on an Alpha. I so wnader what caused this. It had been reporting correctly for over 2 years.Lance Harra |
|
|
|
|
|
|
Incorrect Transaction log Usage