Edit

Best Practices for Maintaining BizTalk Server Databases

  • Article

This topic lists some best practices for maintaining BizTalk Server databases.

  • Make sure the SQL Server Agent is running on the SQL Server. When the SQL Server Agent is stopped, the built-in BizTalk SQL Server Agent jobs that are responsible for database maintenance cannot run. This behavior causes database growth, and this growth may cause performance issues. For information about monitoring SQL Server Agent Jobs see Monitoring SQL Server Agent Jobs.

  • Make sure the SQL Server LDF and MDF files are on separate drives. Having the LDF and MDF files for the BizTalkMsgBoxDb and BizTalkDTADb databases on the same drive may result in disk contention.

  • Do not enable message body tracking, if not required. Frequently, you may want to enable message body tracking while you develop and troubleshoot a solution. If so, make sure you disable message body tracking when you are done. If you keep message body tracking enabled, the BizTalk Server databases grow. If you have a business need that requires you to enable message body tracking, confirm that the TrackedMessages_Copy_BizTalkMsgBoxDb and DTA Purge and Archive SQL Server Agent jobs are running successfully.

  • Typically, smaller transaction logs cause better performance. To keep the transaction logs smaller, configure the Backup BizTalk Server SQL Server Agent job to run more frequently. For more information, see the BizTalk Server Database Optimization white paper (https://go.microsoft.com/fwlink/?LinkId=153594).

  • Use the BizTalk Server Best Practices Analyzer (BPA) to evaluate an existing BizTalk Server deployment. The BPA performs numerous database-related checks. You can download the BizTalk Server Best Practices Analyzer tool from BizTalk Server Best Practices Analyzer tool.

See Also

Checklist: Maintaining and Troubleshooting BizTalk Server Databases Large-growing BizTalk Server Database Tables