%3CLINGO-SUB%20id%3D%22lingo-sub-1434903%22%20slang%3D%22en-US%22%3EMultiSubnetFailover%20connection%20option%20in%20BizTalk%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1434903%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22lia-align-justify%22%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%22%3EThere%20are%20many%20questions%20in%20the%20community%20about%20BizTalk%20Server%20supporting%20MultiSubnetFailover%20connection%20option%20while%20working%20with%20BizTalk%20databases%20in%20Availability%20Group.%20This%20article%20will%20clarify%20some%20of%20the%20doubts%20related%20to%20where%20it%20is%20supported%20in%20BizTalk.%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-justify%22%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-justify%22%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%22%3EBizTalk%20Server%202020%20is%20updated%20to%20use%20the%20new%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252FSQL%252Fconnect%252Foledb%252Foledb-driver-for-sql-server%253Fview%253Dsql-server-ver15%26amp%3Bdata%3D02%257C01%257Cparikshit.gupta%2540microsoft.com%257C60b575a697324f9f4a0108d8074c8da5%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637267372656202829%26amp%3Bsdata%3DIbcxjeZ8Sx3dfs%252BVXZli2%252FV15%252FixPwuJZSs2CdUdBYk%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EMicrosoft%20OLE%20DB%20Driver%20for%20SQL%20Server%3C%2FA%3E%26nbsp%3B(MSOLEDBSQL)%20for%20its%20internal%20working%20when%20connecting%20to%20BizTalk%20Databases.%20Older%20versions%20of%20BizTalk%20Server%20use%20legacy%20OLEDB%20or%20SQL%20Server%20Native%20Client.%20Though%20both%20SQL%20Server%20Native%20Client%20and%20new%20Microsoft%20OLE%20DB%20Driver%20has%20support%20for%20MultiSubnetFailover%20connection%20option%2C%20BizTalk%20Server%20does%20not%20set%20this%20connection%20option%20in%20the%20connection%20string%20when%20connecting%20to%20BizTalk%20Databases%20in%20SQL%20Availability%20Group%20or%20Failover%20Clustering%20Instance.%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-justify%22%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-justify%22%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%22%3EFor%20connection%20to%20SQL%20Server%20using%20WCF-SQL%20adapter%2C%20BizTalk%20Server%20(starting%20with%20BizTalk%20Server%202016)%20does%20support%20setting%20MultiSubnetFailover%20connection%20option.%20WCF-SQL%20adapter%20uses%20ADO.NET%20provider%20(System.Data.SqlClient).%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-justify%22%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%22%3EWhen%20working%20with%20user%20database%20in%20Availability%20Group%20or%20FCI%2C%20MultiSubnetFailover%20connection%20option%20can%20be%20set%20to%20True%2C%20using%20binding%20property%20MultiSubnetFailover%20in%20adapter%20configuration.%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-justify%22%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252FSQL%252Fdatabase-engine%252Favailability-groups%252Fwindows%252Flisteners-client-connectivity-application-failover%253Fview%253Dsql-server-ver15%2523SupportAgMultiSubnetFailover%26amp%3Bdata%3D02%257C01%257Cparikshit.gupta%2540microsoft.com%257C60b575a697324f9f4a0108d8074c8da5%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637267372656207812%26amp%3Bsdata%3DYnsF8OamD8iUcWm%252FBhvis0CMTTEvbWne6C0VjE14MMs%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3ESQL%20Server%20Availability%20Group%3C%2FA%3E%20documentation%20recommends%20specifying%26nbsp%3BMultiSubnetFailover%3DTrue%26nbsp%3Bwhen%20connecting%20to%20a%20SQL%20Server%20availability%20group%20listener%20even%20if%20the%20availability%20group%20only%20spans%20a%20single%20subnet.%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-justify%22%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fsql%252Frelational-databases%252Fnative-client%252Ffeatures%252Fsql-server-native-client-support-for-high-availability-disaster-recovery%253Fview%253Dsql-server-ver15%26amp%3Bdata%3D02%257C01%257Cparikshit.gupta%2540microsoft.com%257C60b575a697324f9f4a0108d8074c8da5%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637267372656212810%26amp%3Bsdata%3DadkKU4hmVIkDK0cz07QGHX681acI%252F3Yq25yCG6%252B9zfA%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3ESQL%20Server%20Native%20Client%3C%2FA%3E%20documentation%20recommends%20not%20specifying%26nbsp%3BMultiSubnetFailover%3DYes%26nbsp%3Bwhen%20connecting%20to%20something%20other%20than%20an%20availability%20group%20listener%20or%20Failover%20Cluster%20Instance.%20This%20may%20result%20in%20a%20negative%20performance%20impact%2C%20and%20is%20not%20supported.%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-justify%22%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%22%3EDefault%20value%20for%20MultiSubnetFailover%20in%20WCF-SQL%20adapter%20configuration%20is%20True.%20When%20creating%20receive%20location%20or%20send%20port%2C%20remember%20to%20set%20this%20property%20correctly%20according%20to%20target%20SQL%20Server%20topology.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1434903%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20many%20questions%20in%20the%20community%20about%20BizTalk%20Server%20supporting%20MultiSubnetFailover%20connection%20option%20while%20working%20with%20BizTalk%20databases%20in%20Availability%20Group.%20This%20article%20will%20clarify%20some%20of%20the%20doubts%20related%20to%20where%20it%20is%20supported%20in%20BizTalk.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1434903%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ebiztalk%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EBizTalk%20Adapters%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EBizTalk%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

There are many questions in the community about BizTalk Server supporting MultiSubnetFailover connection option while working with BizTalk databases in Availability Group. This article will clarify some of the doubts related to where it is supported in BizTalk.

 

BizTalk Server 2020 is updated to use the new Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) for its internal working when connecting to BizTalk Databases. Older versions of BizTalk Server use legacy OLEDB or SQL Server Native Client. Though both SQL Server Native Client and new Microsoft OLE DB Driver has support for MultiSubnetFailover connection option, BizTalk Server does not set this connection option in the connection string when connecting to BizTalk Databases in SQL Availability Group or Failover Clustering Instance.

 

For connection to SQL Server using WCF-SQL adapter, BizTalk Server (starting with BizTalk Server 2016) does support setting MultiSubnetFailover connection option. WCF-SQL adapter uses ADO.NET provider (System.Data.SqlClient).

When working with user database in Availability Group or FCI, MultiSubnetFailover connection option can be set to True, using binding property MultiSubnetFailover in adapter configuration.

SQL Server Availability Group documentation recommends specifying MultiSubnetFailover=True when connecting to a SQL Server availability group listener even if the availability group only spans a single subnet.

SQL Server Native Client documentation recommends not specifying MultiSubnetFailover=Yes when connecting to something other than an availability group listener or Failover Cluster Instance. This may result in a negative performance impact, and is not supported.

Default value for MultiSubnetFailover in WCF-SQL adapter configuration is True. When creating receive location or send port, remember to set this property correctly according to target SQL Server topology.