SQL Server 2005 to SQL Server 2008 migration

  • Hi,

    I am totaly new to database. In my project the database is going to get migrated from sql 2005 to SQL 2008. As a tester what kind of testing should I perform, so that I can give the confirmation to the client that everything got migrated correctly?

    Thanks,

    Golak Senapati

  • First, Microsoft supplies a tool called the Upgrade Advisor. You can download it. Run that against the existing databases to ensure there are no issues for the upgrade. Fix anything it brings up. In my experience, that takes care of the vast majority of the issues within SQL Server. After that, the most common problems I've seen are connectivity from the older app. Test that. Once you've gotten through these two things, you're mostly covered. But to get completely covered, you just have to do a thorough set of functional tests. If you don't have this automated, start working on that.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • After migrating to SQL Server 2008, how can I get to know that all the tables are migrated successfully with its data (accurate data)?

  • You could use a tool like Redgate's Data Compare.

  • Yes, as mentioned by @Grant use "Upgrade Advisor" for SQL Server 2008. Check this blog post where I used the same for upgrading to SQL Server 2012, link: http://sqlwithmanoj.wordpress.com/2012/09/02/upgrade-to-sql-server-2012-use-upgrade-advisor/[/url]

    This tool lets you run compatibility test against SQL Server database, SSIS, SSRS, SSAS, etc. and generate reports for the same.

    The reports will let you know what could break and what will be the fix and online links for the same for more help.

    For data compare there are lot of data compare tools, but you can create your own SQL test scripts to compare data in both the environments.

  • golak_senapati (9/20/2012)


    After migrating to SQL Server 2008, how can I get to know that all the tables are migrated successfully with its data (accurate data)?

    It's a backup and restore, or an attach, or an in-place upgrade. You're not exporting data out and then exporting it back in. It's the exact same database it was. Everything moves or you get failures. If you get failures, you'll know. It's not going to be subtle like a missing table or missing or modified row. It's going to be a major allocation error that will show up in DBCC check or the entire process will fail. The data and the structures will move, assuming you pass the migration checks, because it's no different than running a restore operation.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 6 posts - 1 through 5 (of 5 total)

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