none
AlwaysOn availabilty in BizTalk Server 2016 RRS feed

  • Question

  • What is new feature of AlwaysOn availabilty in BizTalk Server 2016?
    Wednesday, August 9, 2017 10:15 AM

Answers

  • Hi Jitendra,

    Always On Availability Groups is available starting with SQL Server 2016/Biztalk Server 2016.  In previous versions to BizTalk 2016, BizTalk did not provide support for AlwaysOn SQL HA, because DTC was not available, but now that it “is supported”. Windows Server 2016 and SQL Server 2016 now allow MSDTC transactions to be supported by AlwaysOn Availability Groups. 

    The most notable is that BizTalk requires at least 4 SQL Instances for it’s databases, this is because the current implementation of MSDTC supported by AlwaysOn Availability Groups does not support transaction inside of the same SQL Instance, which BizTalk uses extensively.

    You can read in detail here: https://www.art2link.com/biztalk-2016-sql-server-2016-alwayson/

    https://www.linkedin.com/pulse/high-availability-biztalk-server-2016-alwayson-groups-paul-endras



    Rachit Sikroria (Microsoft Azure MVP)

    • Marked as answer by Jitendra-Yadav Thursday, August 10, 2017 3:46 PM
    Wednesday, August 9, 2017 11:43 AM
    Moderator

All replies

  • SQL Server 2016 is the first (and only) edition to support AlwaysOn for BizTalk Server 2016. The reason is lack of support for MSDTC between BizTalk’s SQL Server databases and other transactional resources. For this reason, High Availability for the database layer in BizTalk scenarios has traditionally been solved by using Windows Server Failover Clusters (WSFC), typically with an active-passive configuration.

    Please read more about it on following blog post

    Read This Before Implementing AlwaysOn for BizTalk Server 2016

    and technet 

    BizTalk Server 2016: SQL 2016 AlwaysOn

    If you want to know a particular issue then please feel free to post your queries. 


    Cheers,HTH

    Naushad Alam http://alamnaushad.wordpress.com/

    When you see answers and helpful posts, please click Vote As Helpful , Propose As Answer , and/or Mark As Answer

    Wednesday, August 9, 2017 10:44 AM
    Moderator
  • Hi Jitendra,

    Always On Availability Groups is available starting with SQL Server 2016/Biztalk Server 2016.  In previous versions to BizTalk 2016, BizTalk did not provide support for AlwaysOn SQL HA, because DTC was not available, but now that it “is supported”. Windows Server 2016 and SQL Server 2016 now allow MSDTC transactions to be supported by AlwaysOn Availability Groups. 

    The most notable is that BizTalk requires at least 4 SQL Instances for it’s databases, this is because the current implementation of MSDTC supported by AlwaysOn Availability Groups does not support transaction inside of the same SQL Instance, which BizTalk uses extensively.

    You can read in detail here: https://www.art2link.com/biztalk-2016-sql-server-2016-alwayson/

    https://www.linkedin.com/pulse/high-availability-biztalk-server-2016-alwayson-groups-paul-endras



    Rachit Sikroria (Microsoft Azure MVP)

    • Marked as answer by Jitendra-Yadav Thursday, August 10, 2017 3:46 PM
    Wednesday, August 9, 2017 11:43 AM
    Moderator
  • Thanks but it still not clear please explain with an example
    Wednesday, August 9, 2017 12:08 PM
  • So, don't over think it.

    That just means that you can now use SQL Server AlwaysOn Availability Groups for BizTalk Databases.  This is in addition to SQL Server AlwaysOn Failover Clustering which has been supported since the beginning of BizTalk Server.

    Unless your DBAs are insisting on using Availability Groups, Failover Clustering is still the most practical and widely used option.

    Wednesday, August 9, 2017 1:52 PM
    Moderator
  • Hi Jitendra,

    Always On Availability Groups is available starting with SQL Server 2016/Biztalk Server 2016.  In previous versions to BizTalk 2016, BizTalk did not provide support for AlwaysOn SQL HA, because DTC was not available, but now that it “is supported”. Windows Server 2016 and SQL Server 2016 now allow MSDTC transactions to be supported by AlwaysOn Availability Groups. 

    The most notable is that BizTalk requires at least 4 SQL Instances for it’s databases, this is because the current implementation of MSDTC supported by AlwaysOn Availability Groups does not support transaction inside of the same SQL Instance, which BizTalk uses extensively.



    Rachit Sikroria (Microsoft Azure MVP)


    Thanks Rachit
    Thursday, August 10, 2017 3:47 PM