none
SCCM current Brnach - SQL downgrade from Enterprise to Standard RRS feed

  • Question

  • Dear All,

    I've three sites, 1) Primary stand alone  with current branch 1702, 2nd)Distribution point 3rd)Distribution point. 

    Initially we have installed this setup with SCCM 2012 with MS Sql enterprise 2008, and later on last year in November have migrated to current branch 1702 with SQL 2012 enterprise edition refer below.

    Microsoft SQL Server 2012 - 11.0.5058.0 (X64) 
    May 14 2014 18:34:29 
    Copyright (c) Microsoft Corporation
    Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor).

    Now the thing is my management want to change MS Sql version from Enterprise to Standard edition, I came to know from one of the whatsapp group of SCCM experts it requires lot of activities to be done for this. May i ask if you can guide with the right way along with the checklists, advantages/disadvantages, impact, what all are the backups to be follow etc.. in order to make this happen successful ? .

    Thanks for your support as always. 


    Anil Suthar

    Thursday, August 15, 2019 2:37 AM

All replies

  • I've three sites

    You mean that you have three servers?

    current branch 1702

    This hasn't been supported in well over a year now. You should upgrade to supported version ASAP.

    There is no direct way to downgrade the SQL Server edition. The best that you can do is perform a lateral migration of the ConfigMgr DB from the current Enterprise edition instance to a new Standard edition instance. Note that this can actually be on the same server but if you already have a separate server hosting the DB, it's best to do this to a new server.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, August 15, 2019 2:52 AM
  • Thanks jason for response, i've three servers. 

    May i ask if you can guide with the right way along with the checklists, advantages/disadvantages, impact, what all are the backups to be follow etc.. in order to make this happen successful ? .


    Anil Suthar

    Thursday, August 15, 2019 2:56 AM
  • This blog post lays out everything necessary as this is no different than a normal DB move: https://blogs.technet.microsoft.com/configurationmgr/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server/

    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, August 15, 2019 2:58 AM
  • Thanks this looks older but a good post.. But i still doubt on below contents from the link you provided

    Quote.

    The new SQL Server should be running the same or higher version of the previous SQL Server. It’s possible to have a SQL Server that was running the Cumulative Update 4 (source database) and now you’re moving the database to a server that is running Cumulative Update 6, however if you are moving to the same version of the SQL server, please try to keep them alike to avoid any unwanted results. 

    Unquote..

    My primary stand alone site and and SQL are in same server, Since the performance is slow and it requires huge hardware resources hence planning for separating of SQL server. What are the possibilities, please advise. 


    Anil Suthar

    Thursday, August 15, 2019 3:15 AM
  • You are asking about moving to a new *edition* of SQL Server. The statement above is about the *version* of SQL server. Edition and version are two different things.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, August 15, 2019 3:22 AM
  • So it it possible to move from enterprise to the Standard edition, on a brand new SQL server ?

    Anil Suthar

    Thursday, August 15, 2019 3:25 AM
  • Yes, that's exactly what I've written above and the purpose of this thread.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, August 15, 2019 12:35 PM