Changing Compatibility Levels - do or die?

  • Hi... this is sort of a loaded question.

    I have several DBs in one instance some of which are 80 compat level and others which are 90. My question / assumption is that when I change the compatibility level from 80(2000) to 90(2005) that I may invalidate certain stored procs, etc... because of any changes (depricated features) between the two levels.

    A couple of specific questions.

    1. Once I change (up to 90) can I successfully change back to 80 in case of issues?

    2. I'm dealing with some vendor-supported apps, so I would of course consult the vendors first, but is there a best practice that says all my dbs should be the same compatibility level?

    Thanks for your advice... Any notes on this topic are appreciated.

    Nick

  • 1) yes you can change back

    2)It would depend on how responsive your vendors are at making code changes, from an admin / development point of view it does make it easier if they are all the same level, but it is by no means absolutely neccesary.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply