SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Compatibility level issues with SQL Server 2000 (80) in 2008 R2 Standard environment


Compatibility level issues with SQL Server 2000 (80) in 2008 R2 Standard environment

Author
Message
SQL_ME_RICH
SQL_ME_RICH
SSCrazy
SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)

Group: General Forum Members
Points: 2402 Visits: 1596
I've done some light research already, but just wanted to start this thread for later purposes. I have a system that was recently migrated (not upgraded) from a 2005 Standard environment to a 2008 R2 standard environment. The database is a 2000 db (compatibility level 80). Now - I have upgraded this database through some T-SQL that created the complete set of objects into the 2008 R2 environment (data included), into a QA/TEST environment, and it has had no issues. However - the older version of the db is showing some weariness in it's new PROD environment. This is going to be a tough sell for me to convince the customer (with things currently not working all that great) to upgrade it now, but my best chance is to have them try to duplicate the issues they are having in PROD, over in QA. The only difference in the two environments between the db's one was created as a (100) while the other is still in it's original form (80).

So - my question is this. Has anyone out there had weirdness from their db in 2000 mode in a 2008 R2 environment? Some of the things that are happening are as follows:

- User process not working the same as before (e.g. login screen has an additional step that is now happening where you have to log in twice).
- User reporting is showing delete records that are no longer in the database.
- Search processes are reporting errors related to fields in the db.

Nothing has changed in the web code. Thus - I have concluded that the issue is with the db's compatibility mode. These problems are not occurring in the QA/TEST version (as I previously stated, they have gone through that with no issues to date, so there doesn't appear to be any "old code" issues), but in PROD - no workie.

I know this sounds like I have answered my own question, but if anyone can share/shed any light on this issue (with any experiences of your own), I would appreciate it (so as to give this full due diligence).

Thank you all in advance.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search