Changing compatibility level - on the fly

  • A vendor of ours wants to change the compatibility mode of their databases from 90 to 80. Sounds like they want to do it while the system is online and users are working.

    Bad idea?

    TIA

  • Is there application the only thing app hitting that database? If so, and they are confident that there will be no adverse affects then go for it. Make sure you take a full backup just before just in case.

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • Yes, its their app and only their app in the db. But we here in IS are the ones that look bad if the users start logging errors. Flip side is its a 24/7 system so we would like to avoid any outages.

  • I guess I'm not so much worried about the DB as I am users logging errors and some kind of outage. I can get a backup beforehand and am certainly able to keep the 80 and 90 full and log backups seperate. Still, when something goes wrong I hate hearing "3rd party" from our vendors, so I'm sure our user community would hate to hear "3rd party" from us.

  • Switching compatibility does nothing more than restrict/enable the ability to use certain TSQL enhancements added in SQL2005.

  • It should not be a problem... If they ask you to change it, it would only mean one thing. Their app does not work well with 2005. They must have developed it in SQL 2000.

    -Roy

Viewing 6 posts - 1 through 5 (of 5 total)

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