BizTalk SQL Agent Jobs

Execution of the BizTalk Server SQL Agent jobs are crucial for managing the BizTalk Server databases and for maintaining optimal performance. The Backup BizTalk Server job is the only supported method to backup the BizTalk Server databases and requires that all of the BizTalk Server databases are configured to use the SQL Server full recovery model. See BizTalk Server Log Shipping for more information about using the SQL Server full recovery model when configuring the SQL Agent Backup BizTalk Server job This job must be enabled to ensure a healthy BizTalk Server environment.

The MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb SQL Agent job is designed to run indefinitely. As a result the SQL Agent job history may not indicate that this SQL Agent job has successfully completed, this behavior is by design. If there is a failure, the job will restart within 1 minute and continue running unabated. Therefore, failure notifications for this job can typically be ignored. If the job history for the MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb SQL Agent job indicates that this job is constantly failing and restarting then further investigation into the cause of the failure/restart cycle may be required.

The MessageBox_Message_Cleanup_BizTalkMsgBoxDb SQL Agent job is the only BizTalk job that should not be manually enabled because it is initiated by the MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb job. The DTA Purge and Archive SQL Agent job maintains the BizTalk Server tracking database by purging and archiving tracked messages. This job reads every row in the table and compares the timestamp of each row to determine if the record should be removed. When troubleshooting the BizTalk Server SQL Agent jobs, verify that all SQL Agent jobs except the MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb are completing without errors.

2 Responses

  1. […] BizTalk SQL Agent Jobs: Paul Gu explains the BizTalk SQL Agent jobs […]

  2. zhn says:

    what happen if I execute backup using normal backup , i.e from SEM or BACKUP DATABASE command?