Typically a performance problem can be narrowed down to one of the following components of a BizTalk Server environment:
·A receive adapter or the system from which the adapter is receiving documents. For example, if documents are being received by the HTTP adapter at a suboptimal rate then the problem may be with the HTTP receive adapter or with the client that is posting to the HTTP adapter.
·An orchestration service instance.
·Performance of the SQL Server that hosts the BizTalk Server databases.
·A send adapter or the system that the adapter is sending documents to. For example, if documents are being sent by the SQL adapter at a suboptimal rate then the problem may be with the SQL send adapter or with the computer running SQL Server that the SQL adapter is updating.
Use the following guidelines to help identify the components of the BizTalk Server environment that are performing poorly:
·Capture any warnings or errors generated in the BizTalk Server or SQL Server Event Viewer.
Once the poorly performing component has been identified, follow the appropriate guidelines to help resolve the issue: Guidelines for resolving performance problems related to send and receive adapters
·For information about troubleshooting problems with BizTalk Server adapters, see “Troubleshooting BizTalk Server Adapters” in BizTalk Server Help at http://go.microsoft.com/fwlink/?LinkId=154240. This section contains general troubleshooting information including information about how to set up logging for certain adapters, and information that can be used diagnose network problems, problems with MSDTC, problems with the registry, problems with the file system, and problems with IIS.
·For information about troubleshooting problems with MSDTC, certificates, Enterprise Single Sign-On, and SQL Server, see the appropriate section of “Troubleshooting BizTalk Server Dependencies” in BizTalk Server Help at http://go.microsoft.com/fwlink/?LinkId=154242.
Guidelines for resolving performance problems related to orchestrations
Guidelines for resolving performance problems related to SQL Server
·SQL Server Profiler can be used to capture Transact-SQL statements that are sent to SQL Server and the SQL Server result sets from these statements. Since BizTalk Server is tightly integrated with SQL Server, the analysis of a SQL Server Profile trace can be a useful tool for analyzing problems that may occur in BizTalk Server when reading from and writing to SQL Server databases. For information about how to use SQL Server Profiler, see “Using SQL Server Profiler” in SQL Server Books Online at http://go.microsoft.com/fwlink/?linkid=104423.
·SQL Server Management Studio can be used to execute SQL statements directly against SQL Server databases. This functionality may be useful for querying the BizTalk Server databases or for updating the BizTalk Server databases in certain scenarios. For more information about using SQL Server Management Studio to execute SQL statements, see “Writing, Analyzing, and Editing Scripts with SQL Server Management Studio” in SQL Server Books Online at http://go.microsoft.com/fwlink/?linkid=104425.