Post reply

Compatibility Setting 7.0 Within 8.0 Environment - Pros and Cons?

  • May 12, 2004 at 9:44 am

    #82672

    Hello,

    Environment: Server 2000; MSSQL 2000/SP3; all databses using 8.0 compatibility setting (default).

    We are currently migrating databases from MSSQL 7 to MSSQL 2000. I have one application vendor that developed their app using MSSQL 7.0. They are suggesting (strongly) to set and leave the database compatibility setting at 7.0 within the MSSQL 2000 environment "just in case".

    What would be the advantages/disadvantages with doing this ie: having a 7.0 database run within an 8.0 environment ie: query optimizer; statistics? performance?

    Many thanks. Jeff

  • May 12, 2004 at 11:56 pm

    #506234

    The compatibility settings is for backward compatibility of some T-SQL/Stored Procedures. Some of this may have some impact on performance, but it all depends on which T-SQL Statement or System Stored Procedure and how you use it!

    Kindest Regards,

  • May 13, 2004 at 1:37 am

    #506245

    I wouldn't recommend to set the compatibility mode to 7.0.

    Sooner or later you (or your app vendor) have to migrate your app to the actual SQL Server version (2K, Yukon...). And once you are in a productive environment it will be much harder to get acceptence from your users if THEN there will be some problems.

    Yes it it a hard work to do a migration( I've done several migrations from Sybase 4.2 to SQLServer 6.0, then from 6.0 to 7.0 then from 7.0 to 2000), but this is absolutly not a solution to put back the compatibility mode.

    This job must be done sooner or later and the sooner the better.

    This is my opinion

     



    Bye
    Gabor

  • May 14, 2004 at 8:03 am

    #506491

    Hi, thanks for the responses. Doe the &.0 database within the 8.0 environment still use the 8.0 query optimizer?

    Many thanks. Jeff

Viewing 4 posts - 1 through 3 (of 3 total)

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