Purpose: Since SCCM acts differently depending on the SQL-version, you might be interested to find out, which version is actually installed in your SCCM environment.
Once upon a time Microsoft released a list of supported SCCM configurations. The list also includes all the supported versions and what does it actually mean when you have one of the specific versions installed. Because of this it might be relevant for you to check the SQL version on which you are running your system and take note what it is capable of.
Purpose: When you create bloated SQL queries, you might need to shape them further.
You understand your query, but there just seem to be so many things that must be taken into account. You know that they will not alter the context of your report in a way that could lead to missing information. Therefore you have decided to stop working on the bloated SQL query and use the Report Builder as a tool to shape the query as you see fit.
Purpose: Query SCCM Collection Variables and Values in MS SQL Reporting services (SQL)
There is a suprize waiting for you if you thought you could add variables and values into your collections and query the results using Microsoft SQL Report. Finding the correct attributes from the SQL tables is straightforward, but that is not the real problem.
Purpose: When you create long reports, this makes them easier to read
When you are receiving hundreds or thousands rows of data – your report quickly becomes hard to read. If you are unfortunate and need to read the data yourself, help yourself out with a basic trick. Create a conditional formatting for your report. SQL Report Builder’s conditional formatting is a nice additional touch to your reports and it just might make the report readable for someone else too.
Purpose: Query all the relevant Collection Memberships, defined by you.
After a while, your workstations might be members of many different Device Collections. If you need to point out which collections are actually relevant in some scenarios, you need to use prefixes in your Collection Names. With these prefixes, you can filter out unrelevant collections and create a report, which only shows the relevant Device Collections.
Purpose: Create a Report that allows a user to select the limiting Collection from a drop down list
When you are creating more complex reports with the Report Builder, you will begin to use different kind of parameters with queried values. One of the most common SCCM parameter is the Collection parameter. This guide is valid when you need create your report and let a user to limit it to a single collection.
Purpose: Requirements to correctly use SQL Server Report Builder on an external workstation
Should you need to use the SQL Server Report Builder from an external workstation (not directly from the SQL Server where the Report Service Point is installed), you will need to add the SQL server certificate to the external workstation. This will allow the external workstation to function properly with all of the Report Builder actions.
Purpose: Create a Central SQL Report Data Source (else you need one in every custom report)
Once you take upon the quest of creating reports using SQL Reporting Services, you will soon notice that you are doing the same task in every report that you create. Therefore you should create a centralized data source that your reports will be using. This will save you time and nerves (so you can create even more reports, yey!)
Purpose: Query SCCM 2012 database for all created Applications and sort them by Date
If you need to query details about Applications in SCCM 2012, you cannot do that in WQL. The Admin Console currently supports only to query the old Package-format applications. Should you require information about the new Applications that were introduced in SCCM 2012, you need to use SQL and play with the SQL Server Report Builder to get the report into SCCM.