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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-01-14 : 08:27:13
|
| Patty writes "Currently running SQL Server 6.5 SP 5A upgrade on WINNT 4 SP 6A (I know.. I know.. in the middle of upgrading..) We have a process that dumps the transaction log every 15 minute. This process has been running for over 5 years. In the past, the transaction log size has always been under 500 megs for a week's worth of changes. Recently the transaction log size has jumped up to 1.4 gigs by noon on the first day. Does the transaction log only track insert, update and deletes - committed changes - or does it really maintaining all changes - even those that are not committed? Was able to pinpoint a specific timeframe when the transaction log increase 500 megs in 15 minutes. However, the changes to the database in no way reflected those amount of changes. Is syslogs corrupt? Is there a translation for the OPS Codes in the syslogs table. Is there an easy way to read the transaction log? Any ideas or suggestions would be appreciated. Thanks, Patty" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-01-14 : 12:20:03
|
| You can read the transaction log if you purchase Log Explorer from Lumigent. As far as why it is suddenly growing faster, I would run SQL Profiler (I think it was called SQL Trace in 6.5) during the time that you saw the increase within the 15 minute timeframe. That tool will allow you to see what transactions are occurring. I would seriously doubt that syslogs is corrupt, but you might want to check just in case: DBCC checktable (syslogs). I don't know anything about the OPS codes, but I think that the above tool will give you what you need. |
 |
|
|
|
|
|
Unusually Large Transaction Log