August 16, 2012 at 7:45 am
Since the only way to go from Enterprise to Standard edition is to uninstall enterprise and then install standard. I would like to know what I will lose after attaching the databases. Will jobs and SSIS packages have to be created again? has anyone ever done this or have any good links containing procedures?
August 16, 2012 at 7:53 am
Jobs, logins, linked servers, server side DDL triggers, logon triggers, SSIS packages, database mail etc etc will all be lost.
I have attached a powershell script which will export all SSIS packages from MSDB to file system.
Take a look at SP_REVLOGIN, to script out logins.
The rest would need to be scripted or documented so that it can be re-created.
If you can and you have spare hardware, do this side by side as its a big task to do, that way you also have a quick rollback method should it all go wrong.
August 16, 2012 at 3:18 pm
Would backing up and restoring msdb and master solve some of the loss issues?
August 16, 2012 at 4:44 pm
I'm wondering also if restoring the system dbs along with user dbs might work if using same machine? Do you have a way to test this, I'd be interested in knowing?
--------------------------------------------------
...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully 😀
August 17, 2012 at 1:35 am
MSDB you probably wont have any problems with, but master you might as thats the "server" db, unsure if there would be some flag or data in master to say this is an Enterprise server or a Standard server.
Would be one to test out though if you did have a second server you could install enterprise, then uninstall, install standard.
August 17, 2012 at 1:41 pm
The project is a little ways down the road but I will try that and let you guys know. The install of standard will be on the same machine so i will be testing it.
August 20, 2012 at 7:00 am
You should be able to do this via the Edition Upgrade option, I am sure we have done this.
Go to Microsoft SQL Server Configuration Tools, and navigate to SQL Server installation Center then click the Maintinance link and choose Edition Upgrade.
You should be able to put in your Standard Edition license key. You will have to restart SQL Server before it can take effect.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply