none
TFS 2013 -> TFS 2017 upgrade and database "compatbility level"

    Question

  • After our TFS 2013 (sql 2012) -> TFS 2017.1 (Sql server 2016.1) upgrade I noticed the TFS 2017 databases are still at sql2012 compatibility level.  Is there any reason why I shouldn't change the compatibility level to 2016?

    TIA,

    edm2

    Thursday, March 30, 2017 6:11 PM

Answers

  • Hi edm2,

    Thank you for posting here,

    Actually it's based on your database, you can check the difference between Compatibility Levels.

    You can change the level if the features that involved in your old database are not removed or changed in the new levels.

    So, we don't suggest you change the Compatibility Level if you are not sure about which sql features involved.

    Best Regards.


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by edm2 Wednesday, April 05, 2017 12:37 PM
    Wednesday, April 05, 2017 9:33 AM

All replies

  • Hi edm2,

    Thank you for posting here.

    The act of changing the compatibility level tells the database to change its feature set. That is, some features will be added, but at the same time some old features will be removed. So there is a possibility that it may introduce unexpected results if change the compatibility level, also may cause many hidden and unexpected application errors. Please reference this article for more information.

    Please see this article for Differences Between the Compatibility Levels.

    Best Regards.


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, March 31, 2017 5:40 AM
  • Andy,

    That's a great answer but to be honest I'm surprised, as these are Microsoft databases over which the end user has no control, that changing the compatibility level could actually have a potential impact.

    edm2

    Monday, April 03, 2017 11:47 PM
  • Hi edm2,

    Thank you for posting here,

    Actually it's based on your database, you can check the difference between Compatibility Levels.

    You can change the level if the features that involved in your old database are not removed or changed in the new levels.

    So, we don't suggest you change the Compatibility Level if you are not sure about which sql features involved.

    Best Regards.


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by edm2 Wednesday, April 05, 2017 12:37 PM
    Wednesday, April 05, 2017 9:33 AM