- This topic has 6 replies, 1 voice, and was last updated 9 years, 5 months ago by
.
-
Posts
-
-
What could be the cause of the
c:\\Program Files\\Microsoft SQL Server\\MSSQL\\Data\BizTalkMsgBoxDb_log.LDF
file is 5.5 Gb large? Last week it was only 4 Gb. It eats my space on the disk.
What can be done? Can it be, that I have done a mistake somewhere in some settings?
It’s the server, and there are no more free space, so in few days the system will crash. -
It runs automatically, but the .ldf file grows and grows.
The DataBizTalkMsgBoxDb.mdf file is only19 Mb.
Why can then the log file so big? Can I delete the logs by hand? Or are there a Stored Proc in the SQL that makes it?
Today, the disk has 0 byte free space. There must be a way, to clean the log file. I don’t like to reinstall the server.There are another server I use, there the log.ldf is only 1.75 Mb. In the setting I didn’t find any difference.
-
There is a \”Backup BizTalk Server\” Job, and I tried to run it, but it stopped with an error. The backup itself was complete (I get the backup files), but at the second step(\”MarkAndBackupLog\”) it runs into an error: the sp_MarkAll stored procedure can’t finish.
Can it be, that the log file’s growing comes from here?
How can I set the job to run correctly? I set the Backup’s name, the file’s place.In the SQL Server Enterprise Manager I checked the properties of the BizTalkMsgBoxDb. I saw, that the log file has unrestricted file size (by default), and I can’t set it to lower. I can’t delete it, because it is the primary .ldf file.
-
Do you have SQLAgent running.
There are a number of SQL jobs continuously cleaning and archiving the Biztalk databases. You need to have SQLAgent set for automatic start.
-
Are you backing up the Biztalk Databases.
The log files basically stores all the transactions that occur on the database. This allows a rebuild of the database from a backup and reapplying the logged transactions.As the MessageBox is a transitory database, it only stores stuff that is in-process or about to be copied to the BiztalkDTADb, it should remain fairly small.
However each transaction against the database will create a log record, even when data is deleted.Because the Biztalk databases are all interlinked there is a Backup job provided but this must be setup to run.
-
I thnk you need to find out why the transaction log backup is failing.
Here are some links to some useful info on Biztalk backups.[url]http://sydbiz.org/Home/tabid/36/ctl/Details/mid/414/ItemID/6/Default.aspx[/url]
[url]http://dallas.sark.com/SarkBlog/mholdorf/archive/2004/06/14/261.aspx[/url]
[url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/operations/htm/ebiz_ops_backuprestore_zsbv.asp[/url]
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.