Transaction log on master full

[slimmer]

When executing a script to update our database, the sql is being suspended due to the transaction log on master being full. Once I dump the log on master, not the database I am updating, our queries work fine.

The master database has no options set and I cannot add any to master however the database we are updating does have the option to trunc log on chkpt.

Can anyone explain why the log on master is filling up and not the one on the database I am updating?

Help is appreciated.

 

[LadyNaureen]

how did you dump the log on master database?

 

[slimmer]

I dumped with the command
dump transaction master with no_log

 

[LadyNaureen]

If you execute the following command then I master transaction log will not be used.

exec sp_diskdefault 'master', 'defaultoff'
exec sp_diskdefault 'your_db_name', 'defaulton'

 

[slimmer]

Thank you for your help!