Management Partner Training 2004 Microsoft Operations Manager 2005: Creating Advanced Reports Thomas Theiner Program Manager Windows & Enterprise Management Division Thomas Theiner Program Manager Windows & Enterprise Management Division

Agenda Pre-requisites SQL Server 2000 Reporting Services MOM SDK Views and DW Views Best practices in creating MOM Reports New End-user Reporting experience The new Reporting Templates for MOM 2005 How to create your own Report

What you should take away from here What does it take to create SQL 2000 Reporting Services Reports for MOM How to start your own Report Development with MOM 2005 Standards and Best Practices Where is time wisely invested while developing

Pre-requisites Win2000 with SP4, all editions Windows 2003, all editions, XP ASP.NET 1.1, IIS 5.0 or later installed and configured, MDAC 2.6 or higher. SQL Server 2000 SP3a. For Windows 2003, the computer must be configured as an application server. For Windows 2003 to use the network service account to run the ReportServer service, you need SQL Server QFE 859. To download the QFE, go to Microsoft Support Report ManagerWeb Install Visual Studio 2003 (one of the Visual Studio.Net Standalones) Install SQL 2000 Reporting Services according to your SQL Version Install the System Center Data Warehouse Default website accessible through /Reportserver System Center Data Warehouse Reports through /reports

SQL Server Catalog Report Server XML Web Service Interface Report Processing Delivery Delivery Targets ( , SharePoint, Custom) Rendering Output Formats (HTML, Excel, PDF, Custom) Data Processing Data Sources (SQL, OLE DB, XML/A, ODBC, Oracle, Custom)Security Security Services (NT, Passport, Custom) Office Custom Application Browser SQL Server 2000 Reporting Services Architecture

Step 1: What to think about planning Reports Using Parameters to handle large data volumes Report header allow to chose Parameters Parameter types are  Filtering A filter is a field where to whole results are impacted  Sorting Allow to sort the columns in a Report  Grouping Allows to display data in groups and reduce the amount of data presented. Data collection Data should be collected by MOM that you can Report on. If not already done you to create the logic to collect the data

Step 2: What you should not do Don’t do a simple 100 pages long list - develop the Report based on a scenario e.g. IIS Server Reports were planned as: “give me all IIS Servers with the supported options and capacity to decide where I host that application” or “show me what Server has which Version of ASP.NET installed” The faster you get to your result the better – details can be on a linked Report

Step 3: What Reports should look like

Managed Service Provider Scenario Set: High volume of Servers (Perfcounter, Events, Alerts, etc) Out of the box we provide a range of reports which allow to get a good overview Call: Get summarized Information I want to show Customers how their Servers are doing Work on the Management Packs to get the missing data – use overrides or disable rules which are not useful. Group Customer Servers into groups Create reports based on these groups and summarize data.

Managed Service Provider Scenario Report

Set and follow Standards Use a Reports folder outside of “Microsoft Operations Manager Reporting” to not have your Reports overwritten Do not overload Reports with too much data - choose Portrait or Landscape (Letter or A4) as a Standard If you use a single graph don’t let the User scroll – fit it on one page If you are using multiple graphs keep the same height

Reporting Services Settings This is the setting in Visual Studio Reporting about where to put the Reports on the Reporting Website Set Data Source to SCDW Reason: If you deploy the Reports you want to have the Data Source installed on the Target System. As this is the MOM Data source you can re-use it.

SQL 2000 Reporting Services Tips & Tricks Don’t install SQL Server 2000 Reporting Services to be the default Website – it might break other Websites Test export the Report first to PDF, then to Excel to see the results during your development SQL Server 2000 Reporting Services does not support multi-select in Parameters. Use Computergroups instead Reports execute automatically when opened – watch out what you put in as Parameter defaults SQL Server 2000 Reporting Services does not support multiple queries for a single group – if a query is getting to complex use Stored Procedures and call the from the Report

Tips & Tricks – cont. Convert all UTC date from DB to Local date using this function in the SQL Query dbo.fn_ToLocalDate(Date, GETUTCDATE(), GETDATE()) display the Server/Agent Name with Domain name attached eg. COALESCE(CD.ComputerDomain_PK+'\'+CD.ComputerName_PK,CD.ComputerName_PK) Have a no data text available in the description of the Report. The no data areas offered by Rosetta are too small. When you collect data explain which Rules need to be enabled for this Report in the no data text. Use “Begin Date” and “End Date” as standard parameters Print Sort By and Sort Order as standard parameter on the Report together with all filters entered Use SCDW as datasource name Have a runtime of no longer than 30 sec Users don’t like to wait

Working with large volumes of data Example: Parameter selection

Working with large Volumes of data

Working with large volumes of data Show only relevant Information Toggle field visibility by logical group headers

Hiding details

MOM 2005 Reporting Templates Five Templates for easing your work Basic Settings for an international Report are previewed Reporting Guide was released to TAP customers describing every step in detail

Querying data Where to get the data? We will publish the Data Warehouse Views Schema at RTM  This is an example

Deployment of reports Command line tool: RptUtil.exe creates.xml file which can be imported using the Adminconsole The XML file can contain 1-n Reports /action:Action - import or export. /file:Full path to the import or export file. /url:Url of the report server. /reportpath:Path to the report or report folder to be exported. /fromdsref:Name of the "from" datasource reference to fixup. /todsref:Name of the "to" datasource reference to fixup. /datasource:Name of the datasource to fixup. /dwserver:Name of the datawarehouse server used to fixup the datasource. /dwdb: Name of the datawarehouse database used to fixup the datasource. cd "E:\Program Files\Microsoft System Center Reporting\Reporting" rptutil.exe /file:e:\myalertlatency.xml /nowarn /reportpath:"/custom reports/alert logging latency" Example for a Batch file to export a Report to xml:

Summary What you have seen in this presentation:  All the steps needed to create Custom Reports for MOM  Pre-requisites, SQL Reporting Services, MOM Views  Best Practices, Tools, Templates Try it – custom Reporting is possible now

Attend a free chat or web cast List of newsgroups us/default.aspx MS Community Sites Locate Local User Groups Community sites

© Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.