Multiple BizTalk 2020 server on single instance of SQL server 2019 RRS feed

  • Question

  • Dear BizTalk Experts,

    For multiple development environment setup, Can we configure multiple BizTalk2020 server environments on only one Sql 2019 server instance (AG) ? Does it possible to configure BizTalk product databases with custom names ( i mean side by side BT-DBs for multiple environments ) on one Sql 2019 server instance  .

    If yes then, could you please share any reference article or document  to achieve that?

    Thanks & Regards,


    Wednesday, September 30, 2020 7:50 PM


All replies

  • You probably can, but it goes against recommendations.  Also see this older thread Multiple BizTalk server on single instance of Sql server 

    Yes, you can use custom names for the BizTalk DBs, but again, I would avoid doing so.

    • Proposed as answer by Leo Erlandsson Thursday, October 1, 2020 6:39 AM
    • Marked as answer by BizDevmks Thursday, October 1, 2020 11:24 AM
    Thursday, October 1, 2020 3:08 AM
  • Even if using same SQL computer, I would recommend to have multiple SQL instances to not confuse databases and risk of developers overwriting each others' DBs or mess up or mistakely configure wrong SQL Agent jobs. You can install lots of SQL instances on same SQL server. Then you know also which BizTalk is using a lot of resources (CPU, disk, tempdb etc). Else for dev you could use other separate SQL server so each dev has one SQL and one BizTalk with lower specs instead. There is of course more need of patching etc, so sometimes a bit more work, but it can be less disruption if each developer can handle his own SQL instance or SQL computer rebooting and testing new patches etc as/when he/she wishes. 

    In Azure you can now use the new Azure Shared disk (currently P15 minimum can share disk between 2 computers) to setup SQL FCI (traditional failover cluster instance), clustered MSDTC instead of SQL AO AG avoiding the extra AG disk/network sync/performance between the active and passive node. Windows 2019 can run SQL 2016 or SQL 2019 with S2D storage (multiple data disks) also for the shared disk for MSDTC so that is other alternative.

    There was issue sometimes with SQL 2019 CU2-CU4 so skip those SQL CUs. 

    Friday, October 9, 2020 12:15 PM