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(22.400000000000002, 64%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EG%3C/text%3E%3C/svg%3E)
I was curious as to whether updating SQL Server to version 2016/17/18 while maintaining BizTalk-related databases (BizTalkMgmtDd, BizTalkMsgBoxDb, etc.) in 2016 compatibility mode will cause any issues with BizTalk. Upgrading SQL to 2017 enables us to use new features for non-Biztalk databases.
![](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(73.60000000000001, 11%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMY%3C/text%3E%3C/svg%3E)
One concern is that this is not a supported configuration as defined in the Hardware and Software Requirements for BizTalk Server 2016, which means that if you ever run into an issue with the environment, Microsoft may either refuse to provide help or provide support on a best effort basis.