migration and consolidation SCCM + SQL

matteu31 467 Reputation points


I need to migrate this infrastructure : 1 server with SCCM installed and some roles 2012R2 1 server with SQL installer 2012R2 + SQL 2012

I would like on my target to consolidate it on 1 server 2019 with SQL 2019.

Can I do migration + consolidate on the same step or do I need to first consolidate my source to have 1 serveur 2012r2 with sql 2012 on my SCCM server and after migrate it to 2019 with sql 2019 with backup / restore ?

Thanks you for your help.

Microsoft Configuration Manager
0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. matteu31 467 Reputation points

    Thanks for your answer.

    Unfortunately Microsoft 2012r2 doesn't support SQL2019.
    I would like to consolidate it on 2012because I know it's on supported state.

    The environment is not complicated.

    Is it not ok to do :

    Use actual configuration and 2server -> 1 server.
    I find this : https://deploymentresearch.com/moving-the-configmgr-current-branch-database-to-another-server-as-in-back-to-the-primary-site-server/
    On this server I will have Windows 2012r2 + SQL 2012.

    Then, I build new server and I can do a backup restore scenario on SQL 2019.
    I need to keep the same name + improve database compatibility.

    What do you think about it ?

    In any case, I will have to install SQL twice (1 to consolidate and 1 for final destination).
    I know I can migrate DB from SQL 2012 to 2019.

    1 person found this answer helpful.

  2. Pa_D 1,071 Reputation points
    0 comments No comments

  3. matteu31 467 Reputation points

    Thanks for your answer but i think you read it too fast.

    I will probably

    1) migrate my sql 2012 on my sccm server
    2)2012 to 2019

    0 comments No comments

  4. Amandayou-MSFT 11,051 Reputation points

    Hi @matteu31 ,

    Based on my experience, if the environment is not complicated, we could build up two 2019 servers, install the SCCM and SQL, and then migrate them, finally consolidate them.

    And about the issue of migration, we could try the following steps:

    1.In-place upgrade to SQL 2019 on the old SQL 2012 R2 server.
    2.Migrate SQL DB to new server (2019).
    3.Backup/restore SCCM primary site to the new OS server (same name for the server).
    4.SQL and SCCM same box (Server 2019 and SQL 2019).

    Similar post could be referred to this article:

    About consolidate our source to have 1 server 2012r2 with sql 2012, we could refer to this article:
    Note: This is non-official Microsoft article just for your reference.

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  5. Ulv 81 Reputation points

    The best practice is as @Amandayou-MSFT has mentioned, ensure the feature matrix is compatible. The server supports the SCCM version, Database supports the Server version.

    Take backups, of database and servers, as well as configuration settings of SCCM.

    Build up the new environment, migrate over, smokescreen testing and validate setup.

    Best regards,

    0 comments No comments