locked
SCCM 2012 Database Replication RRS feed

  • Question

  • We are looking to replicate our SCCM 2012 database. The hierarchy is very simple, 1 primary site (no CAS). It does not appear that SCCM 2012 supports database replicas with this configuration. Am I missing something or is this really not supported?

    For the inquisitive, we have 70+ business units who are capable of developing and running their own reports against SCCM. There is a wide variety of skill levels amongst those business units and we end up with some extremely inefficient queries. If we were able to point the reporting server and all of these queries against a replicated database, it would reduce our need to monitor which reports are resource hogs.

    Alternate configurations, such as transaction log shipping, also interest us.

    Thursday, June 21, 2012 6:54 PM

Answers

  • I know other people replicate the SQL databse. It's not a feature within SCCM itself but I think it is a SQL feature.


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

    Thursday, June 21, 2012 8:32 PM

All replies

  • I know other people replicate the SQL databse. It's not a feature within SCCM itself but I think it is a SQL feature.


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

    Thursday, June 21, 2012 8:32 PM
  • Also, CM 2012 DB replication comes into picture (in actual terms) if you've Mutiple primary sites along with CAS.

    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopcnair.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.


    • Edited by Anoop C NairMVP Friday, June 22, 2012 2:19 AM
    • Proposed as answer by TorstenMMVP Friday, June 22, 2012 7:03 AM
    • Unproposed as answer by TorstenMMVP Friday, June 22, 2012 7:03 AM
    Friday, June 22, 2012 2:18 AM
  • Also, CM 2012 DB replication comes into picture (in actual terms) if you've Mutiple primary sites along with CAS.

    Which does has nothing to do with the question of the original poster. He wants to replicate the database just for reporting purposes and it would not make sense to set up a CAS and multiple primaries just because of reporting. So John's answer is correct.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, June 22, 2012 7:04 AM
  • SQL Server is capable of doing replication or transaction log shipping. In the case of the SCCM database, what is the best replication method? Snapshot and transactional replications do not play well with the timestamp data type in the SCCM database. Merge replications work, but modify the schema to include a uniqueidentifier column to every table (timestamp fields are recalculated as the data is replicated).

    Transaction log shipping also requires changing the database recovery model to something other than simple, but it does get the data over to another SQL server.

    Neither of these options seem to fall under a "supported" config. At this time, we will probably further explore the transaction log shipping option because it:

    1. eliminates the possibility of merged data going the wrong direction from a 'reporting-only' database.
    2. should preserve timestamps in the replica.
    3. does not change the SCCM database schema by adding a uniqueidentifier column.
    4. does not require adding the complexity of a CAS just for SCCM to do replication for us.
    Friday, June 22, 2012 7:47 PM