Database Reference
In-Depth Information
How to do it...
The tasks discussed in this recipe are as follows:
• System Center Configuration Manager Schema primer
• Exploring the schema using
Microsoft SQL Server Management Studio
(
MSSMS
)
• Exploring the schema using the System Center Configuration Manager console
System Center Configuration Manager (2012 and above) primer
The schemas that we will discuss in this section are the Microsoft SQL Server views used
for reports. The overall database schema involves a whole lot more, including the informa-
tion retrieved from
Windows Management Instrumentation
(
WMI
) classes and the in-
frastructure components that make up the SCCM deployment.
When you install SCCM in the SQL Server that hosts the database, two view types are cre-
ated using the static and dynamic table information. The static view type is what data is
known, and it does not change for the specific SCCM environment deployment. The dy-
namic view types are data types that are created and deleted over the life time of the de-
ployment. Examples of dynamic views type are collections, inventory extensions, and
when you enable asset intelligent classes. The following table provides a list of the view
categories and their brief description:
View category
type
Description
Application
Management
This is a view used to create reports on application deployments and associated artefacts, such as packages and programs. It is
joined to a collection view to scope the report.
Client Deploy-
ment
This is a view category for client deployment and notification status reports.
Client Status
You use the views in this category for client health check and status reports.
Collection
There are two view types in this category. Collection membership views that list members and collection property-only views.
Compliance
Settings
These are the compliance settings (formerly DCM) specific views that you use to create compliance state reports.
