Post reply

Upgrading a database compatibility from 6.5 to 2000

  • July 15, 2008 at 1:36 pm

    #71640

    Hello,

    I have an old server running SQL 2000 SP4 build 2040. I found that there are serveral databases running under compatibility mode SQL 6.5. Does anyone know if there are any issues in change the mode to 8.0?

    Thanks

    -Ryan

  • July 15, 2008 at 1:48 pm

    #843383

    You really shouldn't have any issues changing the model. I haven't had to go from 65 to 80 but I have gone from 70 and have had no issues.

    It would certainly be a great idea to watch the SQL Server logs and the application logs for a while to make sure that nothing has been affected by this though. 😉

    David

    @SQLTentmaker

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

  • July 15, 2008 at 2:03 pm

    #843392

    The compatibility mode changes the way keywords are handled in SQL Server. There were lots of words that were valid in v6.5 that became reserved in v70 and above (ie TOP).

    I'd be careful about changing this unless you go through the database and look for keyword changes. Those are your biggest worry and they could cause things to stop working.

  • July 15, 2008 at 2:06 pm

    #843395

    All

    Thanks for all your help. Right these databases are on a dev. system. So worse comes to worst. I'll restore from a backup prior to the compatibility mode change.

  • July 15, 2008 at 9:42 pm

    #843481

    I remember 1 scenario last year when we migrated a prod server from version 7 to 2000. The migration is successful but after users login the system they begin sending print screens of the error they encountered. I tried to set the compatibility to 70 and the user's stop receiving the error so i guess compatibility may affect applications. If you have in-house software better seat with them first

    "-=Still Learning=-"

    Lester Policarpio

  • July 15, 2008 at 10:07 pm

    #843488

    FYI : changing the database compatability mode only changes how the optimizer parses your queries. The most likely issue that you will encounter is SQL code that the application uses is not compatible with the compatability mode you select. If this happens, all you need to do is to change back to the original value. You shouldn't need to restore the database since the underlying data storage is exactly the same regardless of the compatability mode. The way that data is stored may change between versions but not because of the compatability mode.

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

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