Having a strong knowledge in SQL Server is something that time and again comes in very handy. Whilst I might be able to whip up a decent stored procedure, or set up a decent batch job, when it comes to the more complicated DBA type work I am still very much a learner.
I recently left a solution deployed to the test environment running over the weekend to see how it would cope over a decent period of time. When I got in on Monday there was over 60k server instances in the dehydrated or ready to run state. This was not what I wanted to see, definitely not in the expected or acceptable results ball park.
Turns out the cause was the there was no hard drive space left which meant log files could not be written to, intermediate xml messages coukdn't be created etc
I thought perhaps that the file output of the orchestrations had just written too much data to the poor 20gb hd in use. This turned out to be a false assumption as the culprit was the BizTalk Message Box database' log file. It had expanded to 12gb.
So in SQL Management Studio you can right click on the BizTalkMsgBoxDB and go to Tasks -> Shrink -> Files and select the log file. You'll then be able to resize the log DB.
Just as importantly is the right click Properties -> Files dialog. This lets you set auto growth options for the log file.
No comments:
Post a Comment