July 21, 2010 at 3:46 am
Hi there
We have a 2005 Standard Edition on a hosted machine. We wish to upgrade to 2008, but use Express or Web Editions instead (the provider is charging us €300 pm for Standard, compared to €30 pm for Web and nothing for Express). As there is no direct upgrade path from 2005 Standard to either of these 2008 editions, I'm wondering if anyone has done this before and would have any advice going forward. None of the databases on the existing server are bigger than 5 GB and we don't use the agent other than for reindexing. Backups are done via a third party tool and we don't use any of the extra features of Standard Edition so there's no real reason to stick with it.
I presume the best way would be to rename the existing instance, then install the 2008 instance using the original instance name and then move logins/databases. I've upgraded before, but always to the same edition, so I'm wondering if there's any gotcha's that might arise in this instance.
Thanks
Steven
July 22, 2010 at 1:32 pm
If your going to Express or Web it is a downgrade which is why you may not find it if you have been searchign for upgrades.
I would suggest taking a copy of a backup from standard and installing express on a dev box and attempting to restore the database.
I do not know if you can restore a standard backup on express but I would say try it and see.
Keep in mind express does not have SQL Agent, so if you utilize that for backups you will need to schedule them a different way.
You may need to re-create your strucutre and transfer in all of your data in order to achieve this.
Twitter: @SQLBalls
Blog: http://www.SQLBalls.com
Channel: https://www.youtube.com/@Tales-from-the-Field
July 23, 2010 at 7:20 am
I agree with Bradley, this is a downgrade.
I have not done the particular one you are facing but I personally did about 25 Enterprise Edition to Standard Edition.
After checking for specific functionality to be lost during the downgrade - general procedure was...
1- Take a full backup of the current database
2- Script security
3- Script jobs
4- Script database creation for all user databases
5- Shutdown SS
6- Take a full O/S level backup
7- Remove current SS
8- Install new SS
9- Pre-create user databases, security, jobs - using scripts taken on #2, #3 & #4
10- Restore user databases on top of pre-created ones
11- Check security, jobs, etc
12- Gather fresh stats on all objects
I would test procedure in a test box before hitting production.
Hope this helps.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.July 23, 2010 at 8:20 am
Thanks for the advice fellas, much appreciated. The hosting company are insisting they do this themselves, but I'll ensure they follow the advice you've given above.
Regards
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply