SCOM 2012 - Datawarehouse without SQL Reporting

Cyclops3590
Cyclops3590 used Ask the Experts™
on
I am deploying SCOM 2012 soon.  The design I was given shows nothing for a SQL reporting services server anywhere.  I'm told that since part of the design calls for a datawarehouse database that we must have a SQL reporting services server installed as well.

What I want to know is why.  It's my understanding that the mgmt servers will populate the DW db and via the consoles be shown to users.  So what does the SQL reporting services add for me and if it truly is required to be deployed when deploying the datawarehouse db, why it's required.  What breaks if it's not there or does it just not let you install the DW db even?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
The management servers synchronously populate your operational and data warehouse databases during normal operation.

Your operational database contains all of the data that allows you to use SCOM from day-to-day.  Everything you see in the monitoring pane is being pulled out of the operational database.  It usually has about 7 days worth of statistics stored in it.  After 7 days elapses, the old data is groomed out of the database.  If you look at the performance reports from this pane, there will be no data available outside of this small window.

Your Data Warehouse contains aggregated historical data, kept for however long you have your retention period set to.  To use the data you need something that will let you access and manipulate the data into a useful format, namely a reporting tool.  In SCOM The SQL Reporting Server is that tool.  
During installation, the SCOM install changes the default security settings on the SQL Reporting server so it can use one of its security profiles to transparently present and run reports from the console.  (This process is why SQL RS on whatever system you put it on can only be used by SCOM)
The installation adds the "Reporting" pane to the SCOM console.  What you see in this pane is a direct view into the content on the SQL Reporting Server and the scheduling and report authoring capabilities in SCOM are actually just pretty interfaces that hook into the SQL reporting server.

When you install a management pack that contains reports, part of the installation is the automatic load of these reports onto the SQL Reporting Server by SCOM. They will then show in the reporting pane in the SCOM admin console.

So even if you have a data warehouse setup, if you don't have SQL Reporting Services in your SCOM infrastructure, you won't be able to use these reports the product experts have designed for you (and why reinvent the wheel if you don't have to?), you will be missing the reporting section of your Admin console and you will have a huge database full of data you can't easily get at and need to essentially understand the SDK to decipher if you want to report on it from another tool.

(I'm away for about 4 days from here on in so please ask any quesitons you have if this isn't clear but there will be a delay in me responding).
Cyclops3590Sr Software Engineer

Author

Commented:
thanks again for the detailed explanation.  I was hoping this wasn't the case because it seemed odd that if it was required to use the DW data that it would be missing from the arch design.  oh well, one more thing to correct.  :)

thanks again.
Cyclops3590Sr Software Engineer

Author

Commented:
i love verbose answers to general questions.  learn more that way.  thanks

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial