March 4, 2013 at 7:38 am
Hi Team,
I have request from client to degrade few servers due to cost of enterprise edition.
Can you suggest me the plan and things to take care.
My Plan is as below.
1. Backup all the databases.
2. Script logins and jobs.
3. Dettach the user databases.
4. Uninstall the enterprise edition.
5. Install the standard edition.
6. Attach databases.
7. Run login and job scripts.
Please suggest.
March 4, 2013 at 12:52 pm
You're going to exactly the same version as originally, right?
I think it's easiest to just restore all the dbs (other than model) after the switch.
There are so many things in master and msdb that it's easy to miss something trying to script it out.
Restore master first, obviously; see Books Online for details.
Then restore msdb.
Then restore the other dbs.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
March 5, 2013 at 1:00 am
And don't forget to check if the DB don't have an enterprise features before downgrade http://www.sqlskills.com/blogs/paul/sql-server-2008-does-my-database-contain-enterprise-only-features/
March 5, 2013 at 3:43 am
Scott,
Going for the same version from enterprise to standard.
Yes , I will check the enterprise features used in current databases.
March 5, 2013 at 7:56 am
There's no physical db differences from Enterprise to Std, so if the SQL version numbers are the same, you should be able to restore all dbs, including system dbs, from Ent to Std.
Books Online has pretty good guides on restoring system dbs.
Master first; once master is restored, SQL will shut down on its own, so be prepared for that. [If somehow it doesn't, you need to shut down SQL yourself. After restoring master, you should always recycle SQL.]
After SQL comes back up, then restore msdb: naturally make sure you stop SQL Server Agent first :-). After the restore of msdb is complete, you may want to recycle again, even if it's not technically needed, just to be safe.
After that restore the user dbs, which are standard user db restores just like you've always done.
Of course you'll also want to check any linked servers, external permissions, etc., to make sure everything is working as you expect it.
Once you're ready for jobs to start kicking off, you'll restart SQL Server Agent. This may be after only some user dbs, or after all of them. It depends on your specific jobs and their requirements.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply