FAQs Related to SCCM SQL Based Database Replication

SQL Based replication is the biggest change in SCCM 2007 and 2012

5
SCCM View Article Names
SCCM View Article Names
Advertisement

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 2012 primary server SQL DB and Secondary server SQL DB.

List of all Replication Groups and Article Names (Tables) Involved SCCM 2012 SQL DB Replication here.

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 site can’t be controlled !!

2. Why the SQL Database replication between SCCM 2012 secondary server and Primary server throttling option is not there ?

Honestly, I don’t know. But what I can think is there are very less data replicated between primary DB and secondary site DB hence no need to throttle it. I know, still some of us are able to traces GBs of data replicated from SCCM Primary SQL server to secondary server.

More details about this  replication data :- Only 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 secondary server SQL database.

3. Which are the replication Groups come under Replication Pattern called Global Proxy (secondary server data?)? 

In the SCCM 2012 SQL DB, I can see two Replication Patterns names under Global Proxy.

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 which contains 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 which are replicated to SCCM 2o12 secondary server SQL DB. More detailed list in the following table.

It seems Replication IDs are different in each environment so use 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 a 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 table name.

SCCM View Article Names
SCCM View Article Names

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.

We may need to check all the tables which are part of Global_proxy Replication pattern (list of tables is below). I’m not able to find the easy way to do this calculation for all the tables involved. Manual method is to open up the table properties then Storage and check Index Space.

SCCM Table Size
SCCM Table Size
List of Article Names or Tables which are under the category of Global_Proxy replication pattern 

These are the tables which are replicated from SCCM 2012 Primary server SQL DB to secondary server DB.

ArticleNameReplicationID
ActiveDirectoryForestPublishingStatus22
ActiveDirectoryForests22
ActiveDirectoryForestTrusts22
AlertVariable_G022
AlertVariable_G122
AlertVariable_S22
AlertVariableXml_G22
ArticleData21
AutoClientUpgradeConfigs22
AutoClientUpgradeSettings22
BGB_Server22
BootImgPkg_References22
BoundaryEx22
BoundaryGroup22
BoundaryGroupMembers22
BoundaryGroupSiteSystem22
CI_ConfigurationItemContents22
CI_ConfigurationItems22
CI_ContentFiles22
CI_ContentPackages22
CI_Contents22
CI_Types22
CI_UpdateSources22
CIContentPackage22
ClientDeploymentSettings22
ClientKeyData_GP22
ClientKeyDataCertExtend22
ClientPushMachine_G22
CM_SiteConfiguration22
ContentDPMap22
CP_System_Resource_N_ARR22
DeviceDiscoveryTranslation22
DeviceMPSettings22
DistributionStatus22
DPUpgradeStatus22
DrsSendHistorySummary22
InventoryAction22
InventoryClass22
InventoryClassProperty22
MIG_AppVPackageMapping22
PackageContentInfoHash22
PkgAccess22
PkgProgramOS22
PkgPrograms_G22
PkgServers_G22
PkgStatus_G22
PkgStatusHist22
PortalInfo22
ProceduresToForward21
PullDPResponse22
RcmSqlControl22
RcmSqlControlProperty22
RcmSqlControlType22
ReplicationData21
SC_Address22
SC_Address_Property22
SC_Address_PropertyList22
SC_AddressType22
SC_ClientCfg_Property22
SC_ClientCfg_PropertyList22
SC_ClientComponent22
SC_ClientComponent_Property22
SC_ClientComponent_PropertyList22
SC_ClientConfiguration22
SC_Component22
SC_Component_Property22
SC_Component_PropertyList22
SC_Configuration22
SC_Configuration_Property22
SC_Configuration_PropertyList22
SC_GlobalProperty22
SC_GlobalProperty_Property22
SC_GlobalPropertyList22
SC_GlobalPropertyList_PropertyList22
SC_MISCItem22
SC_MISCItemType22
SC_PublicKeys22
SC_RoleType22
SC_SiteDefinition22
SC_SiteDefinition_Property22
SC_SiteDefinition_PropertyList22
SC_SysResUse22
SC_SysResUse_Property22
SC_SysResUse_PropertyList22
SC_UserAccount22
SC_UserAccount_Property22
SC_UserAccount_PropertyList22
SCCMAutoUpdates21
SCCMAutoUpdateStatus22
ServerData21
SiteExchangeKeys22
SitesInfo22
SMSContentHash22
SMSPackageHash22
SMSPackages_G22
Summarizer_SiteSystem22
TS_AppReferences22
TS_References22
TS_TaskSequence22
UnknownSystem_DISC22
Update_SyncStatus22
UpgradeVersionMap21
WebServiceInfo22
WSUSServerLocations22

5 COMMENTS

  1. Hello Anoop,

    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?

LEAVE A REPLY

Please enter your comment!
Please enter your name here