September 12, 2004 at 3:51 pm
Hi,
Could anyone please give me some tips on database conversion. We have a third party application which needs to be upgraded to higher version and the conversion has new objects to be installed and also some new indexes built in the conversion process, any tips/suggestions will be greatly appreciated
Thanks!!!
September 13, 2004 at 9:24 am
Can you expand upon your question a bit? What will be updated to a higher version? The DBMS, or the third party application itself? Did the vendor provide an update script? What problems are you expecting?
--
Adam Machanic
whoisactive
September 14, 2004 at 6:58 am
test test test
Copy your production database to a test database. Run the vendor supplied update scripts (automatic or manual) against the test database. Get your users to test the new system and 'sign it off' as OK. This absolves you of any responsibility if anything is found 'missing' later. This also gives the users a chance to play with the upgraded system so that they don't do anything dangerous with the new system when it goes live. For example, some of the new features may not work as expected (may have bugs) and may corrupt the data. The new features should be thoroughly tested by the users.
Back up the live database somewhere safe. Then do the conversion for real. Make sure the users 'sign off' the live conversion (you will have to let them do some more testing and/or run reports).
Also make sure you have some performance statistics before and after the upgrade (time batch jobs take to run, response times for normal inserts, etc) so you have some facts if you need to go back to the vendor to report performance problems.
Hope this gives you some ideas.
Peter
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply