July 19, 2002 at 8:33 am
Hello,
This weekend, the master database's transaction log filled up and caused my jobs to fail. I am trying (in vain) to discover what is stored in this transaction log that would cause it to fill up. The master database doesn't allow transaction log backups against it, so I just kinda have to allocate lots of space to it to avoid filling up.
Thank you,
Melanie
July 19, 2002 at 8:53 am
Take a look at DBCC LOG here http://www.sqlservercentral.com/columnists/achigrik/sqlserver7someusefulundocumenteddbcccommands.asp otherwise you will need a third party tool such as LogExplorer to look at the logs information. DO you have any inadvertant user tables in the master database?
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
July 19, 2002 at 9:09 am
Hello,
I apologize for my ambiguous request. I am actually trying to find out the kinds of information that would be stored in the master database's transaction log.
Reason I ask is because over the weekend, there was a login connecting to a user database with 750 connections! This then caused an integrity check maintenance plan to fail due to the master db's transaction log being full. This, in turn, kept my database in single user mode and cause our application to fail.
Could the 750 connections held during the weekend cause the transaction log to fill up? The connections are essentially the only thing out of the ordinary.
Thanks!
Melanie
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply