check list for Migrating sql server 2000 to 2005

Question

check list for Migrating sql server 2000 to 2005

Viewing 4 posts - 46 through 48 (of 48 total)

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

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

mahesh.vsp (5/11/2010)
How to recover or make the customer in safer zone without loosing the 5 days data??

Restore the pre-upgrade backup to SQL 2000. Use a tool like Redgate's SQL Data Compare (other vendors likely have a similar tool, you can roll your own with SSIS if you feel brave) to sync the data.

How does a DBA can plan or prepared for such a scenario?????

Same way you plan for any other scenario. Examine the risks, the chances of it happening, examine the options for resolving such a scenario, come up with workable options, test.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Brandie Tarvin SSC Guru Points: 173068 More actions · Answer 2

GilaMonster (5/12/2010)
How does a DBA can plan or prepared for such a scenario?????
Same way you plan for any other scenario. Examine the risks, the chances of it happening, examine the options for resolving such a scenario, come up with workable options, test.

What she said.

If you document everything that needs changing BEFORE you do the switch over, make sure you have all your backups, and do a side-by-side migration, the only thing that can fail as you check off your list is the new hardware / software. And in most cases, you should know within a day if the migration is working.

We've done two migrations already (2 & 1/2, actually) and the BU never even noticed.

Just take your time. And have a checklist of everything (and I do mean everything) you have in your system. Including non-SQL Server items that need to have Connection Strings changed (ODBCs, web.config files, etc.).

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

Oh, and if you've done your testing properly, you'd have found and fixed all the places where the app breaks on the new version, long before you migrated the actual production server.

If you do have a case, after migrating the production server, where something breaks, it means you didn't do your testing properly.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Oracle_91 SSChampion Points: 14548 More actions · Answer 4

Thanks Gila. Just want to confirm how it goes in Real Time.