locked
22 BizTalk Servers connected to 1 SQL Server RRS feed

  • Question

  • Hi,

    In the development environment, technically we can configure BizTalk, by connecting to 1 SQL Server Instance ( BizTalk 2016 on Azure ).

    My question is, is it ok to do so, from a performance point of view. What are the drawbacks.

    Regards,

    Sharmishtha

    Friday, February 1, 2019 6:10 AM

Answers

  • While it will run, technically, you're creating a terrible and quite unproductive situation for your developers  Meaning, you're setting yourself and the developers up to fail.  It's just creating unnecessary problems.

    First, there are no benefits to doing this.  None.  Not even one.

    The biggest problem is that all SQL operations from all 22 BizTalk computers will be single threaded due to the MDOP requirement of the MessageBox.  There is no way around this except...

    Creating 22 separate SQL Server Instances, 1 for each BizTalk computer.  But, this means you will need a very, very large VM to meet the CPU and memory requirements for a usable experience.

    Developers will get in each other way.  No amount of consideration or process will change this.

    There are no licensing or cost benefits to sharing a SQL VM.  Both BizTalk Server and SQL Server have no cost Developer Editions.  If the Developers have Visual Studio Subscriptions, they may be included there.

    All of the above will slow down development costing way more $$ in developer time.

    The correct and best experience is very simple, 1 VM per developer with the entire stack, Windows Server, SQL Server, BizTalk Server and Visual Studio.  Anything else will just creates problems and costs more in lost time than any theoretical (but non-existent) savings.

    • Marked as answer by Sharmishtha Friday, February 1, 2019 1:04 PM
    Friday, February 1, 2019 12:34 PM
    Moderator

All replies

  • for dev machine its ok 1BT and 1 SQL
    Friday, February 1, 2019 10:26 AM
  • I have 22 BizTalk Servers , configured on 1 SQL Server.
    Friday, February 1, 2019 10:32 AM
  • While it will run, technically, you're creating a terrible and quite unproductive situation for your developers  Meaning, you're setting yourself and the developers up to fail.  It's just creating unnecessary problems.

    First, there are no benefits to doing this.  None.  Not even one.

    The biggest problem is that all SQL operations from all 22 BizTalk computers will be single threaded due to the MDOP requirement of the MessageBox.  There is no way around this except...

    Creating 22 separate SQL Server Instances, 1 for each BizTalk computer.  But, this means you will need a very, very large VM to meet the CPU and memory requirements for a usable experience.

    Developers will get in each other way.  No amount of consideration or process will change this.

    There are no licensing or cost benefits to sharing a SQL VM.  Both BizTalk Server and SQL Server have no cost Developer Editions.  If the Developers have Visual Studio Subscriptions, they may be included there.

    All of the above will slow down development costing way more $$ in developer time.

    The correct and best experience is very simple, 1 VM per developer with the entire stack, Windows Server, SQL Server, BizTalk Server and Visual Studio.  Anything else will just creates problems and costs more in lost time than any theoretical (but non-existent) savings.

    • Marked as answer by Sharmishtha Friday, February 1, 2019 1:04 PM
    Friday, February 1, 2019 12:34 PM
    Moderator