Upgrading to 2020.2 does not upgrade database compatibility level to 140

Hi team,

We just did an upgrade from 2019.x to 2020.2 and it worked beautifully. That’s some seriously nice work you’ve done there. One small thing, based on the minimum requirements listed here: https://octopus.com/blog/raising-minimum-requirements-for-octopus-server i was surprised to see that the upgrade-scripts did not set database compatibility level to 140.

Since you require SQL2017, it might be worth considering. I’ve done this manually, and so far it does not seem to introduce any issues.

USE [master]
GO
ALTER DATABASE [Octopus] SET COMPATIBILITY_LEVEL = 140

Hi Kasper,

Thank you for contact Octopus Support.

Good catch on your part! Rest assured, we do look at the SQL db version during the 2019.X to 2020.X update process and halt the process if SQL2017/2019 is not detected. I will, however, pass this information along to our development team to make them aware.

We really appreciate you letting us know. Also, do not hesitate to reach out if you ever have any questions for us.

Regards,
Donny

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.