This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 55.00000000000001%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAY%3C/text%3E%3C/svg%3E)
We currently have BizTalk 2016 Enterprise Server and SQL Server 2016 environments installed on different Windows Server 2016 Boxes. SQL Server 2016 instance also contains other databases needed for our business.
Per Microsoft BizTalk Server 2016 is compatible with SQL Server 2016 or 2014.
I was wondering if upgrading SQL Server to version 2017 but running BizTalk related databases (BizTalkMgmtDd, BizTalkMsgBoxDb etc.) under 2016 compatibility mode would create any issue for BizTalk. SQL upgrade to 2017 will allow us to take advantage of new feature for other non-Biztalk databases. I know it is ideal to use separate SQL Servers for BizTalk and other databases but that is not an option for now. Thank you and appreciate any insight on this.
A family of Microsoft server products that support large-scale implementation management of enterprise application integration processes.
Answer accepted by question author
One issue is that it is not a supported configuration as per Hardware and Software Requirements for BizTalk Server 2016, which would mean that if you ever do have an issue with the environment, Microsoft may either decline to give support, or not be held to any SLA and only offer best effort.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 75%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENE%3C/text%3E%3C/svg%3E)
It has not been tested in BizTalk 2016 so not supported. E g the SSISDB infrastructure (BAM) changed from MSDB in SQL so this may have problems.
BizTalk 2020 supports SQL 2019/2017/2016.
I recommend also to not share SQL instances with other non-BizTalk databases, but instead create multiple SQL instances. You can have many SQL instances on same SQL servers.