BizTalk 2013 Installation and Configuration – Configure SQL Server Network Configuration protocols (Part 10)

  • Sandro Pereira
  • May 19, 2013
  • 3 min read

Under certain stress conditions (such as clients accessing SQL Server from the same computer), the SQL Server Shared Memory protocol may lower BizTalk Server performance. You can resolve this problem by disabling the use of the Shared Memory network protocol in the SQL Server Network Configuration. Also, to facilitate transactions between SQL Server and BizTalk Server, you must enable TCP/IP and Named Pipes in SQL Server.

📝 One-Minute Brief

To ensure optimal performance and reliable transactions in BizTalk Server 2013, SQL Server network protocols must be specifically configured. This guide explains why you should disable “Shared Memory” (to avoid performance bottlenecks) and enable “TCP/IP” and “Named Pipes” (to facilitate smooth communication between the middleware and the database). It provides a quick walkthrough using the SQL Server Configuration Manager.

To configure the protocols for SQL Server:

  • Press the Windows key to switch to Metro UI, type SQL Server Configuration Manager, and click on the SQL Server Configuration Manager option on the Apps menu.
BizTalk Server 2013 SQL Server Configuration Manager
  • In SQL Server Configuration Manager windows, from the left-hand pane, expand SQL Server Network Configuration option and then click Protocols for MSSQLSERVER.
    • Verify that both TCP/IP and Named Pipes are enabled.
      • If not, right-click in the protocol and then click Enable.
      • Repeat to enable the other protocol if necessary.
    • Verify that Shared Memory is disabled.
      • If not, right-click Shared Memory, and then click Disable.
BizTalk Server 2013 SQLNet SQL Server Configuration Manager Protocols for MSSQLSERVER
  • In the left-hand pane, click SQL Server Services, right-click SQL Server (MSSQLSERVER), and then click Stop. After the service has stopped, right-click SQL Server (MSSQLSERVER) again, and then click Start.
BizTalk Server 2013 SQLNet SQL Server Configuration Manager SQL Server Services restart
  • Close SQL Server Configuration Manager.

Related links

Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son. 

Thanks for Buying me a coffe
Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

7 thoughts on “BizTalk 2013 Installation and Configuration – Configure SQL Server Network Configuration protocols (Part 10)”

Leave a Reply

Your email address will not be published. Required fields are marked *

The Ultimate Cloud
Management Platform for Azure

Supercharge your Azure Cost Saving

Learn More
Turbo360 Widget

Back to Top