October 7, 2009 at 9:11 am
I am trying to get an estimate from experienced technicians on how long the SQL upgrade from 2000 - 2005 will take. The importance is the amount of down time that a end user should experience. We have a Electronic Medical Records System in a Drs office and the upgrade is mandatory becuase of the version of there software we are running. We cant shut the office down for the entire day to have this done. Any input on estimated time on this upgrade. We have SQL 200 with 18 Cals. Thanks
October 7, 2009 at 9:58 am
Totally depends on how complex your apps and databases are, for example a sql install can be done in less than 20 minutes and most organisations allocate up to 1/2 a day for an install.
To do an upgrade, I would allow as much time as you possibly can.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
October 7, 2009 at 12:31 pm
Most of your effort while doing an upgrade would go in testing! Get a dev/test environment (ss2k5) run upgrade advisor, test your application extensively, identify the problematic/pain areas(code), come up with a fix for that.. at the end when everything is tested, uat is done, then you will provide a downtime and do everything that you have planned for production and it wont take more than half a day depending on your application's complexity. Identify if its going to be side by side upgrade or Inplace upgrade!
If you want to provide an estimation, go from testing point of view. How many modules/pages/functionality you gotta check.
This could become very handy for you,
All the best!
---------------------------------------------------------------------------------
October 7, 2009 at 12:59 pm
sounds like you are a small shop and may not have the luxury of test environments or being able to do a side by side upgrade (upgrading by migrating to a new server.). As its 3rd party software and they say you have to upgrade its a fair assumption that the application should work after the upgrade
Be prepared though in case of problems if you are doing an upgrade of the existing instance, make sure you can back the upgrade out, in case the upgrade itself fails This would mean an uninstall of SQL 2005 and a reinstall of SQL 2000, so make sure you have the SQL2000 installation software available as well. Backup ALL databases first.
Definitely run the SQL2005 upgrade advisor first which will highlight any potential problems. Available here;
Including all backups and post upgrade work and presuming your database is not huge half a day is a good estimate.
there are things you should do after the upgrade such as reindex, update stats, I can post a script for that tomorrow when I am back at work.
What version of SQL are you currently running? post the results of this query
select @@version
Do you have any data transformation packages (DTS)?
---------------------------------------------------------------------
October 8, 2009 at 9:23 am
haven't heard so don't know if you need or want it but anyway here is a script of post upgrade tasks to perform on a database
---------------------------------------------------------------------
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply