Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

UPGRADE SQL SERVER 2000 to 2008 R2 Expand / Collapse
Author
Message
Posted Monday, July 30, 2012 2:48 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, November 28, 2012 8:16 AM
Points: 7, Visits: 22
Plan to upgrade (side by side) v. 2000 to 2008 R2 and set compatibility level to 90 (not 100) - all application work done by vendor who has agreed to support this initiative.

Use backup & restore to new W.2008 server.

Any issues with this ? Or experiences to share ? Appreciate any feedback.

TIA
Post #1337550
Posted Monday, July 30, 2012 3:02 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, April 11, 2014 7:37 AM
Points: 2,673, Visits: 3,325
Why 90 and not 100? The biggest issues you face are going from 2000 to anything. If you are going to go through the trouble of identifying what is different between 2000 and 2005, why not just do it for what you paid for?

Thanks,

Jared
SQL Know-It-All

How to post data/code on a forum to get the best help - Jeff Moden
Post #1337560
Posted Monday, July 30, 2012 3:20 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 10:42 AM
Points: 20,460, Visits: 14,086
SQLKnowItAll (7/30/2012)
Why 90 and not 100? The biggest issues you face are going from 2000 to anything. If you are going to go through the trouble of identifying what is different between 2000 and 2005, why not just do it for what you paid for?


Agreed




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1337573
Posted Wednesday, August 01, 2012 8:17 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, November 28, 2012 8:16 AM
Points: 7, Visits: 22
TX - agree just that 90 is the min. comp level for future upgrade to 2012. If our vendors can do it why not ?

Any experiences to share here or pointers for what to look out for from the trenches ?

TIA
Post #1338569
Posted Wednesday, August 01, 2012 11:37 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 8:43 AM
Points: 1,201, Visits: 2,661
BEFORE you move off of SQL 2000 run these against the databases. If there are any errors do NOT backup/restore to SQL2008, fix the errors first.

DBCC CheckCatalog
go
DBCC CHECKALLOC
go

After you backup/restore to SQL2008 run the DBCC UPDATEUSAGE(0, N'dbo.tablenamehere') on ALL tables in the database.

Then rebuild ALL indexes on ALL tables so the optimizer will see all of the indexes in the SQL2008 optimizer. Once that is done run a DBCC CHECK DB on the database to make sure there is no corruption at all, then do a db backup so you have a good SQL2008 Recovery point before you open it up to testing and customers.



Post #1338712
Posted Wednesday, August 01, 2012 9:32 PM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, March 21, 2014 9:46 AM
Points: 387, Visits: 1,078
2000 would use Torn_page_detection to check IO level corruption. Better change it to Checksum.
Post #1338930
Posted Friday, August 03, 2012 9:59 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, November 28, 2012 8:16 AM
Points: 7, Visits: 22
Much appreciate the advice. Keep it coming folks !
Post #1339950
Posted Friday, August 03, 2012 10:17 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, April 10, 2014 10:18 AM
Points: 1,769, Visits: 2,800
dbasql79 (8/1/2012)
2000 would use Torn_page_detection to check IO level corruption. Better change it to Checksum.

+1

Do this before rebuilding the indexes - IIRC, checksums are only written when the data/index page is updated.
Rebuilding the indexes should ensure checksums are created for all your data.

I'd recommend setting Compressed Backups as the default & switch on 'Optimise for Ad Hoc Workloads' option, but they're not really upgrade considerations

Have you run the Upgrade Advisor to check your SQL is compat-90 valid? Or is that the application vendor's problem?
Cheers
Post #1339960
Posted Friday, August 03, 2012 10:25 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 4:31 PM
Points: 32,780, Visits: 14,941
Definitely use the upgrade advisor. Watch out for older scripts that check system tables as many of them have changed.

I assume you are doing a test upgrade, but please make sure this is done on another machine. Upgrades in place are tricky, and can leave you stuck. Make sure you have good backups (2 copies) and enough time to reinstall SQL 2K if something goes awry.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1339967
Posted Friday, August 03, 2012 12:50 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, November 28, 2012 8:16 AM
Points: 7, Visits: 22
Have generated Upgrade Adv. reports for 2008 and sent off to the vendors.

Backup restore is the approach from current win. 2003 to 2008 server.

Any 32 bit to 64 bit stuff I need to care about during this process ?

Post #1340056
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse