How can we help you today? How can we help you today?

How to manage people using different versions of Sql Server

Good Evening,

Our Dev team, for various reasons, run different versions of Sql Server with some on 2016 and others on 2019.
When we come to commit our changes using Sql Source Control we are continuously overwriting or having to amend the RedGateDatabaseInfo.xml file.

Is there a way we can ignore the DatabaseVersion property, or set it as a default one that does not compare against users checking in?

Thanks in advance
Paul
PaulBl
0

Comments

3 comments

Sort by
  • DanC
    Hi @PaulBl

    We always advise on having the same SQL Server version across all members of the team to avoid this issue!

    Unfortunately, there's no way to ignore this property and until you're all universal with the same SQL Server version it will continue to be modified.

    Hope this helps!
    DanC
    0
  • PaulBl
    Hi @DanC, thanks for the reply.

    The issue being is that Sql Server version does not necessarily equal DB compatibility levels. All our dev's are using the same compatibility level.

    However Sql Source Control is checking on Sql Server Version instead of compatibility level. Having this changed would fix our issue.
    PaulBl
    0
  • DanC
    Hi @PaulBl

    SQL Source Control will honor the Use Database Compatibility Level option, and if that option is enabled, store the compatibility level in RedGateDatabaseInfo.xml rather than the server version.

    I would advise updating to the latest version if you haven't already.
    DanC
    0

Add comment

Please sign in to leave a comment.