Post reply

SQL 2000 DB on a SQL 2005 Server

  • October 29, 2008 at 9:28 am

    #200413

    I have a sql server 2005 set up. One of the databases is a test db in sql 2000 compatibility mode - the production db is on a sql 2000 server.

    I've noticed that I'm allowed to do many things on this test database cannot actually be performed on the sql 2000 server.

    for example, select * from sys.triggers, select * from sys.columns

    Is there anything that I can set on this test database that will prevent things from occurring that can't actually occur on the sql 2000 server? Moving a script from test to production is the wrong time to find out that I included something that won't run on the 2000 server.

    Thanks,

    Wayne

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes

    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • October 29, 2008 at 10:10 am

    #891335

    not that I know of. It's a type of "forward compatability", translating things so that they work on a 2000 type system. Not intended to emulate 2000 completely.

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

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