Monitoring and Reducing Database I/O Contention

BizTalk Server performance is often predicated upon SQL Server performance, which in turn is often predicated upon disk I/O performance. Therefore, you should monitor and performance-tune disk I/O on the computers running SQL Server that house the BizTalk Server databases.

Monitoring Disk I/O

Because of the database-intensive nature of BizTalk Server, disk I/O can easily become a bottleneck on the MessageBox and BizTalk Tracking databases; this is true even if disk I/O has not previously been a bottleneck for the database files in your SQL Server environment. Thus, we recommend that you proactively measure disk I/O performance for the disks that house the data and transaction log files. For more information about monitoring disk I/O performance using System Monitor, see the SQL Server article "Predeployment I/O Best Practices" ( If you are using a SAN, you may also need specific tools from the SAN hardware manufacturer to measure disk I/O performance.

Separating the MessageBox and BizTalk Tracking (DTA) Databases and Log Files

Since the MessageBox and BizTalk Tracking databases are the most active, we recommend that you place the data files and transaction log files for each of these on dedicated drives to reduce the likelihood of problems with disk I/O contention. For example, you would need four drives for the MessageBox and BizTalk Tracking database files; one drive for each of the following:

See Also

Using the Performance Analysis of Logs (PAL) Tool