Most of the times we can rely on the more general reporting features delivered with SCOM 2007 R2 for reporting purposes. But when you want to design a really nice looking report which is much easier to generate and target you need to dive into report designer or even the even more flexible Visual Studio which

Creating a Custom Report for SCOM 2007 R2 with SQL 2008 reporting in Microsoft Visual Studio 2008

In every business there are several different groups of report users, from chief executives, to business analysts, to operational staff, who all need access to reliable and current data in order to track overall business performance, investigate the effectiveness of individual business functions, or simply for ad-hoc day-to-day reporting.

In most organizations, at least some attempt has been made to meet these reporting needs. Historically, however, the problem has been that the available reports have not always been up-to-date, or even accurate. Furthermore, individual departments have tended to adopt a "silo" approach, using different tools/systems to create reports that are useful within their silo, but not necessarily consistent or compatible with those produced by other departments. In many cases, there doesn’t even exist a shared understanding of the business data that underpin these reports.

SQL Server Reporting Services (SSRS), when it arrived, offered a much-needed means to centralize and standardize reporting across the business, and it has largely delivered. Having used SSRS 2005 for the past 4 years, I’ve found that, with a little effort, it can satisfy most business, ad-hoc, embedded, portal integration, web, and custom reporting needs. However, I’ve also found that small "gotchas" can halt progress and cause considerable frustration, as it’s not always easy to find ways round them in the documentation.

Ten Common SQL Server Reporting Services Challenges and Solutions

Recently I had to connect to a SharePoint List to access some data.  While there
is a data extension
available from Enesys (including a free Community edition) to do this I though
I would first make an attempt using the out-of-the-box options.

The first step was getting connected to any of the list services.  I chose to
start with GetListCollection because it required no parameters (aka it was simple
to use).  Here is what I did to get connected:

Accessing
SharePoint List Items with SQL Server 2005 Reporting Services – Colin Bowern – RockstarGuys.com