There are lots of duplicate views (vcollection, Vcollections) that stores almost the same information. To review and remove those duplicates would ease the use of the database.

Use unique identifiers - in rare cases the resourceid is called itemkey. Or the product code shows up sometimes as Software Code. A unified naming convention would be very appreciated.

Devide information for CI deployments/compliancy, those for applications, Security Upates, Deployment Types and whatnots. Having all stored to one table/view CI_ConfigurationItems is very confusing and very difficult to retrieve.

Outdated versions/revisions (apps, CIs) not in use should be removed also on the CAS by the maintenance tasks.

application data is stored in a XML format only. This is very, very hard to retrieve and link to all other items like Deployment-Types and Deployments. - Information on applications should be stored in a table/view instead.

I often repeat the following actions:

• Verify Component Status (Monitoring - System Status - Component Status)


• Open any Component with Status Warning or Error.


• Verify the Warning or Error is Solved


• Reset All Counts for this Component.

A Typical example: Restart the Site Server.
All Management Points complain that the Site Server is unavailable.
But in they also report the System is Online again.

MP File Dispatch Manager running on the management point "mp.company.com" cannot connect to site server "SiteServer.company.com". The operating system reported error 53: The network path was not found.

Component Status Summarizer detected that the availability of component "SMSMPFILEDISPATCHMANAGER" on computer "mp.company.com" has changed to Online.

The Monitoring System could Verify an Error/Warning MessageID was followed by an Information MessageID that indicates the problem has been solved and change the summary status back to OK.

Just upgraded from 1910 to 2002 and the upgrade failed and had to open a support case. Bottom line our SQL DBA made unauthorized changes to SCCM database and enabled PAGE compression on 370 tables in the SCCM database.

Please add to the pre-req check the running of this SQL query if any tables are set to PAGE data compression fail the pre-req.

SQL to Check: SELECT t.name AS tablename,

   i.name AS indexname,

   p.data_compression_desc

FROM sys.tables AS t
INNER JOIN sys.indexes AS i

 ON t.object_id = i.object_id

INNER JOIN sys.partitions AS p

 ON i.object_id = p.object_id

    AND i.index_id = p.index_id

Where p.datacompressiondesc = 'PAGE'

Report recommendation to turn off PAGE compression using this SQL:
EXEC spMSforeachtable 'SET QUOTEDIDENTIFIER on;alter TABLE ? REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE)'

That will save you from failed ConfigMgr Upgrade nightmare.