This topic lists best practices that you should follow on a weekly basis when to avoid performance issues with a BizTalk Server system.
|Set database auto-growth to a fixed number||- Database auto-growth should be set to a fixed number of megabytes instead of a percentage, especially for the MessageBox and Tracking (DTA) databases. Depending on your BizTalk Server application and throughput, the MessageBox and Tracking databases can get quite large. If auto-growth is set to a percentage, then the auto-growth can be substantial as well.
- If the system is new and the static sizes have not been definitively established, then configure files with the Enable Autogrowth option and specify file growth In Megabytes. The growth increment should generally be no larger than 100 MB (for large files), 10 MB (for medium-sized files), or 1 MB (for small files). See the Appendix B – Recommended BizTalk Server Database Configuration section of the BizTalk Server Database Optimization white paper (http://go.microsoft.com/fwlink/p/?LinkID=153594) for a table with suggested files sizes for each of the BizTalk Server databases.
|Limit the events that you monitor with SQL Server Profiler||Use SQL Server Profiler to monitor only the events in which you are interested. If traces become too large, you can filter them based on the information you want, so that only a subset of the event data is collected. Monitoring too many events adds overhead to the server and the monitoring process, and can cause the trace file or trace table to grow very large, especially when the monitoring process takes place over a long period of time.|
|Configure message batching to increase adapter performance||- Minimize the number of transactions performed by an adapter by combining more than one operation into a single batch.
- Limit the batch size based on the total number of bytes in the batch, in addition to message count. For more information about limiting the batch size, see Configuring Batching to Improve Adapter Performance.
|Adjust the large message threshold||To improve throughput, increase the large message threshold, which lowers the number of large messages that are buffered to disk during mapping.|
|Investigate memory leaks or out-of-memory exceptions in the BizTalk Server process||Memory leaks in BizTalk processes can occur due to varied reasons. See Microsoft Knowledge Base Article 918643, How to troubleshoot a memory leak or an out-of-memory exception in the BizTalk Server process (http://go.microsoft.com/fwlink/p/?LinkId=157212) for information about the scenarios in which a memory leak may occur, and how to fix it.|