FAQs Related to SCCM SQL Based Database Replication Configuration Manager | ConfigMgr. In this post, I’m going to cover 5 questions raised to me and answers that I found.
All these are related to the database replication between SCCM primary server SQL DB and Secondary server SQL DB.
FAQs Related to SCCM SQL Based Database Replication
List of all Replication Groups and Article Names (Tables) Involved SCCM SQL DB Replication here. FAQs Related to SCCM SQL Based Database Replication Configuration Manager | ConfigMgr.
1. Have you ever noticed SCCM 2012 Database Replication Link Schedule or Throttling option is Grayed out in the console?
Yes, Database SQL-based replication between SCCM 2012 Secondary and Primary sites can’t be controlled!! FAQs Related to SCCM SQL Based Database Replication Configuration Manager | ConfigMgr.
2. Why the SQL Database replication between SCCM 2012 secondary server and the Primary server throttling option is not there?
Honestly, I don’t know. But what I can think is there are very few data replicated between primary DB and secondary site DB hence no need to throttle it. I know, still, some of us are able to trace GBs of data replicated from the SCCM Primary SQL server to the secondary server.
More details about this replication data:- Only a subset of Global Data (that is called Global Proxy data) is replicated to SCCM 2012 secondary server SQL DB. Moreover, this SQL (Database) replication is ONE-way replication. The Global Proxy replication data is replicated from SCCM 2012 primary SQL server to the secondary server SQL database.
3. Which are replication Groups come under the Replication Pattern called Global Proxy (secondary server data?)?
In the SCCM 2012 SQL DB, I can see two Replication Patterns names under Global Proxy. FAQs Related to SCCM SQL Based Database Replication Configuration Manager | ConfigMgr.
SQL query :- Select * from vReplicationData where ReplicationPattern = ‘Global_proxy’
ID ReplicationPattern ReplicationGroup
21 global_proxy Secondary_Site_Replication_Configuration
22 global_proxy Secondary Site Data
4. What is ArticleName in SCCM 2012 DB?
Article Names are nothing but Tables that contain actual policy data.
The Replication Groups (mentioned above) are further divided into Article Name based on ReplicationID. To find what exactly is replicated from SCCM 2012 Primary SQL DB to Secondary server SQL DB. We’ve 104 Article Names that are replicated to SCCM 2o12 secondary server SQL DB. The more detailed list is in the following table.
It seems Replication IDs are different in each environment so use the SQL query mentioned in Question 3 to find out replication group IDs Secondary_Site_Replication_Configuration and Secondary Site Data.
Select * from vArticleData where ReplicationID = ’21’ or ReplicationID = ’22’
For example, you can see an ArticleName = ClientKeyDataCertExtend and when you check the table then you can see the table in the same name ClientKeyDataCertExtend. So it seems to me that all article names are referenced back to the table name.
5. How much SQL data will get transferred or replicated from SCCM 2012 Primary server DB to secondary server SQL DB?
Update: We can use exec spDiagGetSpaceUsed size of reach replication groups with table details. Umair Khan helped me to get this information. FAQs Related to SCCM SQL Based Database Replication Configuration Manager | ConfigMgr.
We may need to check all the tables which are part of the Global_proxy Replication pattern (the list of tables is below). I’m not able to find an easy way to do this calculation for all the tables involved. The manual method is to open up the table properties then Storage and check Index Space.
List of Article Names or Tables which are under the category of Global_Proxy replication pattern
These are the tables that are replicated from SCCM 2012 Primary server SQL DB to secondary server DB.
SCCM Related Posts Real World Experiences Of SCCM Admins (anoopcnair.com)
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…
5 thoughts on “FAQs Related to SCCM SQL Based Database Replication Configuration Manager | ConfigMgr”
You can use this for the 5th question which tells you the size of reach replication groups with table details.
Hi Umair ! – Thank you Much Dear!
I missed that stored procedure.
We may have a need to feed downstream reporting teams with data in SCCM 2012. They would like to enrich their reporting with some of the underlying tables from SCCM that gather data related to servers and workstations. Is there any type of best practice documentation or recommendations for transmitting some of these core tables / views downstream?
Hi, I have this scenario:
CAS and reporting with sql 2012
6 primary sites with sql 2012 version.
Is possible migrate the CAS SQL database and reporting database to sql 2017 keeping the 6 primary sites with sql 2012?
what about replication?
I think all the supported versions of sql is fine. I don’t think it’s necessary to have same version of SQL for cas and primary servers.
My recommendations is to perform tests in the lab or pre prod environment before implementing this in production