locked
Migrate SCCM DB to named instance RRS feed

  • Question

  • We have attempted to move the SCCM DB in our environment using the following blog as our guide. (see link below) Scenario: 1 Primary server (Win2012R2), and 3 secondary servers. Primary server holds all roles including Site DB and SSRS Role.  Existing DB is/was SQL2012 Enterprise on the Default SQL instance. We installed SQL2014 Standard to a new named instance (SCCM).  We had to give the new named instance a static port.  The SCCM site maintenance task failed otherwise (error - unable to connect to SQL port).  After setting a static port, site maintenance completed successfully.

    https://blogs.technet.microsoft.com/configurationmgr/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server/

    First off - We assume that what we have attempted is supported. So, if anyone has any info otherwise - it would be appreciated.

    Following the site maintenance, everything seemed to be working.  The secondary sites initially showed link failure, but after 10 minutes reported okay.  So, we then removed the Reporting Services role (still configured to look at the SQL2012 DB).  Then we added it back and pointed it to the new SQL2014 DB/instance.  (created a new SQL2014 reporting DB in the process)

    It was at this point, we noted there were no options in reports. (list of reports is blank)  Additionally, now we noticed that links to all secondary sites were dead.  Site to site replication was dead.  Replication status from the sites report their last send time was around the time we stopped all SCCM services to do the DB migration.

    We tried to kick off a secondary site recovery from within the console for only one secondary site.  It has been stuck in Recovery status for about 16 hours now.  The last time we did a recovery on this site, it only took 30 minutes for the whole process.  It seems like the recovery process is stuck in a loop.

    Have we made a poor assumption that SCCM can be moved to a named instance on the same SCCM/site database server?  

    And if this is possible - what steps have we overlooked?

    In the end - we're just trying to get to a newer version of SQL, but moreover we're trying to eliminate the unnecessary (and expensive) SQL Enterprise license.  Thank you for reading.

    Saturday, August 6, 2016 4:26 PM

Answers

All replies

  • First off moving form SQL Enterprise to Standard is NOT supported. It might work but it is not supported and can fail big time.

    Yes, You can move CM's db to an SQL instance, However is it generally recommend that SQL and CM exist on the same server.


    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    Saturday, August 6, 2016 4:33 PM
  • First - thank you for such a rapid reply.  

    Well - if it's unsupported - then I guess we're stuck with Enterprise, and I'll need to get to work back-tracking the mess that I have created.  It sounds like our problem is less about a named instance - and more about a SQL compatibility (Ent -> Standard).  

    Thank you again for your reply.

    Saturday, August 6, 2016 4:42 PM
  • Sorry to repost so quickly, but I just wanted to clarify in case there was any confusion.  

    SQL2012 Enterprise is installed on the SCCM primary server as the default (MSSQLSERVER) instance.  SQL2014 Standard is also installed on the same SCCM primary server as named instance (SCCM).  

    We weren't attempting to upgrade SQL2012 Enterprise to SQL2014 Standard. (I believe this is impossible, as the installer prevents it)  We have both installed side-by-side - we were attempting to move the DB from one to the other.  I just want to make sure this is the information for which you based your response.

    Thanks!

    Saturday, August 6, 2016 5:03 PM
  • Just to be clear the issue is with the database not the version of SQL and how it get partitioned. If it got parturition (this is an automatic process) then it is not supported to move the database from SQL enterprise to SQL standard.

    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    Saturday, August 6, 2016 5:52 PM