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

testing the SQL sever upgrade Expand / Collapse
Author
Message
Posted Monday, April 18, 2011 7:07 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, April 19, 2011 10:51 AM
Points: 4, Visits: 5
I would like to know the testing approach for sql sever upgrade 2000 to 2008 . Does anybody has any idea??
Post #1094897
Posted Monday, April 18, 2011 8:38 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Monday, October 28, 2013 8:10 AM
Points: 822, Visits: 1,198
Are you planning to do an in-place upgrade? if so what I would do is install a version of 2000 on a different box and apply patches to pring it too the same software version. Then I restored all DB's and used sp_help_revlogin to migrate over all logins. I then did the upgrade and had our developers point some of there applications at this test environment to make sure everything was working ok. If that went well then I ran the upgrade advisor on the prod server. Note you want to run the advisor only nt the actual install which will run the advisor as well. then take a look at the report and verify there are no major issues. pay particular care to any that say before upgrade.

Dan

If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.
Post #1095020
Posted Monday, April 18, 2011 9:09 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, April 19, 2011 10:51 AM
Points: 4, Visits: 5

Thanks for the reply. Actually we are planning to have side by side upgrade. If that is the case what kind of testing approach is good? I would like to cover the all possibly of the testing.
Post #1095055
Posted Monday, April 18, 2011 9:30 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Monday, October 28, 2013 8:10 AM
Points: 822, Visits: 1,198
In a side by side it is very similiar. once you setup the new 2008 DB you can identify applications that connect to your DB's. you will need to work with the correct departments to ensure that they can be installed on a test machine with the ability to point them at the new instance. Once you have restored all DB's you will need to again script all logins and jobs to build on the new instance. Evaluate the any DTS packages independantly. Given the fact that the ugrade whizard does not work all that great it may be better to rebuild the DTS packages as SSIS packes manually. Once all applications are tested and packages built you can set you date for go live. If you keep and changes in cynch between the two environments in the mean time you should simply have to restore the DB's once last time and then repoint all live applications.

It will really depend on you applications and requirments how you go about the actual testing. It may be enough to simply connect and open a few screens or you may need to organize some sort of performance testing. There may also be specific scnarios you have to test. for example if you have any replication setup you would need to define that and then test those connections. If you have reporting services installed that is also another consideration.

the biggest advice I could give is use a method that is best for you to track everything. I write everything out on a white board. Every DB, Job, Replecation, DTS, application anything involved or affected. as they get tested and passed I place a green dot next to them. once everything has been cleared then I can proceed.


Dan

If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.
Post #1095080
Posted Monday, April 18, 2011 9:48 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, April 19, 2011 10:51 AM
Points: 4, Visits: 5
Thank you.
Post #1095090
Posted Monday, April 18, 2011 10:14 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, April 19, 2011 10:51 AM
Points: 4, Visits: 5
Do you have any sample test strategy for sql server upgrade?I would like to see one. Please..
Post #1095122
Posted Monday, April 18, 2011 11:37 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Monday, October 28, 2013 8:10 AM
Points: 822, Visits: 1,198
above the basics no. there is not a really a magic bullet that can be applied to every environment. It unfortunatley requires you to undertand your environment and then customize it based on that. For example I would not use the same Test cases on anyone of my instances as they all serve different applications and functionality. On one instance it is enough to have the developers connect and app and say it worked. others we have to go through a full blown user test an show performance thresholds and the whole ball of wax. Follow the basics and go from there. If you are looking to implement to stadardized process you can treat this as a software change which it really is and follow the software change life cycle. Here is a good example of the process.

http://en.wikipedia.org/wiki/Software_testing_life_cycle


Dan

If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.
Post #1095186
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse