Marin BezicSQL BI Product ManagerMicrosoft EMEA

Enterprise Reporting with SQL Reporting Services

- Management and Scalability –

AgendaReporting Services ArchitectureSetup and configuration Securing your report serverReport and model managementScheduling and subscriptionsScale out

SQL Server Database / SQL Server Agent

Shared Components

Web Service(IIS / ASP.NET)

Windows Service

URL Access SOAP Endpoints

Data

WMI

Delivery

Security

Report Manager

Rendering

Browser DesignTools

ManagementStudio

ConfigurationTool

ReportServer ReportServerTempDB

Reporting Services ComponentsReporting Services Native Mode

SQL Server Reporting Services and SharePoint Integration

SQL Server 2005 Reporting Services SP2 integrates with Windows SharePoint Services to enable publishing, viewing, and management of rich reportsOffice SharePoint Server 2007 “Lights Up”

Report library integration of Reporting Services functionalityRich reports in Dashboards with filter Web Parts

Integration BenefitsNew services for WSS and Office SharePoint 2007 ServersIntegrated User Experience for Reporting Services users

SharePoint Content DB Report Server DB

WSS/OS Report Server

Reporting Services Add-in

RS Viewer Web Part

Report Management

UI

WSS Object Model

SP2 Report Server Web Service

Security Extension

Catalog Synchronizatio

n

WSS Object Model

SharePoint Integration ArchitectureReporting Services SharePoint Mode

Reporting Services 2005 Setup

Reporting Services setup in Microsoft SQL Server 2005 has two modes:

Default ConfigurationFiles Only Installation

Default configuration assumes you want to:Install on default web site (will create new App Pool in Microsoft Windows 2003)Install relational database in same instanceUse service accounts for database connection

Configurations requiring files only setup:Remote catalog databaseScale out deployment (a.k.a. Web farm) installationSharePoint Integration mode

Client Setup includes the Microsoft Visual Studio 2005 shell (Business Intelligence Development Studio)

Upgrading from Microsoft SQL Server 2000 Reporting Services (SSRS)

Setup supports upgrade of “default” SQL 2000 Reporting Services installations

No changes to virtual directories, custom extensions

SQL 2005 Reporting Services supports use of SQL Server 2000 relational database

Caveat: Setup upgrades all components in default instance

Existing reports will continue to workPublished reports and snapshots will continue to work on upgraded Report ServerSQL 2000 reports can be published to SQL 2005 Report ServerOpening reports in the Report Designer will upgrade them to the new RDL schema

Reporting Services Web Service supports existing SOAP endpoint

New endpoints for management and report executionWMI object model has changed

Reporting Services 2005 Configuration Tool

Configuration Tool Features

Virtual directoriesSupports non-default Web sites

Service identitiesDatabase settings

Creation and upgradeScripts can be saved to be applied later

SharePoint integration (SP2)Key managementScale-out initialization

Does not sync settings across machines

E-mail delivery settingsReport processing account

Server Configuration

Management and Configuration Tools

Report ManagerWeb-based viewing and management application

SQL Server 2005 Management StudioSuperset of Report Manager functionality

Reporting Services Configuration ToolWindows-based tool for local or remote configuration of service

Client utilitiesScript HostEncryption Key Management

Custom applicationsWindows SharePoint Services / Microsoft Office SharePoint Server 2007

Enabled in SP2

Report Management

Reports, data sources, and report models are published to SharePoint document libraries

When a report is selected in WSS, the report viewer Web Part calls the report server API to process and render the reportUsers can manage properties and subscribe to reports through WSS UI (calls RS SOAP API)UI includes ability to launch Report Builder to create / edit reports

New report server delivery extension allows for rendered reports to be delivered to WSS document libraries (including Report Center)Design tools (Report Designer, Report Builder, Model Designer) are updated to work with WSSReport Manager is not supported in SharePoint Integration Mode

Reporting Services SharePoint Mode

Report Viewer Web Part

Used in full page view or on Web Part PagesWraps the ReportViewer ASP.NET Viewer ControlHandles report rendering calls to report serverWeb Part Properties

Report: ReportPath, HyperlinkTargetView: AutoGenerateTitle, AutoGenerateDetailLink, ToolBarMode, ParametersMode, ParametersAreaWidth, DocumentMapMode, DocumentMapAreaWidthParameter Default Values

Supports Filter Consumer and Row Consumer interfaces for specifying report parameter values via filter Web Parts

Can slice Excel Workbooks and Reports on a single Web Part page

Reporting Services SharePoint Mode

Management APIs

Web ServiceFor managing content in Report ServerSQL Server 2005 splits API into Management and Execution endpointsBackward compatibility endpoint for existing applicationsFull SOAP API implementation (includes WSDL) w/complex typesAdd service reference in Visual StudioSupports SSL and scripting

WMIUsed for managing service configurationEnumerate instances of Report ServerSupports remote configuration and works even if Web service is not availableNo WMI events (configuration only)

Server NamespaceHierarchical namespace managed in SQL Server databaseFolder metaphor for organizing reports, setting securityItem types

ReportFolderData sourceResourceModel

Items are referenced by path in SOAP API and URL access (for example, /Adventure Works/Sales Report)My Reports feature (off by default) provides users a folder on the server for publishing reports

/My Reports is redirected to /users/<username>/My Reports

Role-Based Security ModelTasks

Sets of low-level operationsItem-level (for example, create report) or system-level (for example, manage jobs)Not customizable

RolesSets of tasksDefault roles installed by default(browser, publisher)Default roles can be customized, new ones createdRoles identified by name, localized

Groups/usersWindows/Active Directory or customauthentication users

Role assignmentsAssociates groups/users with RolesInherited from parent in namespace

SharePoint Integrated Mode in SP2 maps to WSS permissionsItem

RoleAssignme

nt

Group orUser

Role

Task

Operation

Securing Items

Report ManagementReport Metadata is extracted from report definition at publishing and maintained in the databaseNameDescriptionReport DefinitionParameters

Prompt vs. HidePrompt StringDefault Values

Data Source Information (embedded or reference to shared data source)

Report Data Sources

Administrator can set connection type and connection string after publishingCredential Options

Prompt for Windows or database credentialsSecurely stored Windows or database credentialsIntegrated Security (Requires Kerberos delegation; can be disabled in SAC)None (uses report execution account; must be enabled in Configuration Tool)

Shared Data SourcesConnection and credential information stored as a secured object in the namespaceSingle point of management for multiple reportsSharePoint Integration Mode in SP2 can use .RSDS or .ODC files

Report Caching

Execution sessionsAutomatically created for each report executionKeeps consistency between server round trips (images, paging, exporting)Session timeout set in server properties

Cache snapshotsOn-demand reports can be cached between usersCache index is based on parameter valuesCache valid for a specified time after execution or cleared on scheduleLimitations – User-specific expressions (User ID, Language), stored credentials

Tip: Use Null Delivery Provider to deliver reports to cache

Snapshots and History

Execution snapshotReport execution is scheduled, all users get same dataSingle instance of processed reportLimitations: No query parameters or user-specific expressions, stored credentials

History snapshotsMultiple instances of report snapshots for archiving, auditing purposesStored independently of data source, report definitionSystem and report-specific retention policy

Managing Report ExecutionConfigure cache and snapshots via Report Manager or SQL Management StudioSet execution timeouts on a system-wide or per-report basisLong running reports can be stopped manuallyReport Execution Log enables analysis of server usage

Optionally, executions are logged to Report Server databaseIncludes report, format, user, start, end, cache hit, sizeSetup includes SSIS package and sample reports

Scheduling

Management events can be scheduled on the report server

Caching, Subscriptions, History

Schedules are stored in database and integrated with SQL Agent

When triggered, Agent adds entry to queue

Scheduled events are queued in database and polled by Windows service

Shared Schedules

Managed shared schedules independently of reports, subscriptions, or snapshotsChange shared schedule properties

NameDays, times, or frequenciesStart and end dates

Pause and resume shared scheduleExpire a shared scheduleDelete shared schedule

Subscriptions

Subscription triggered by an event (schedule, snapshot creation, external)Delivery extension (e-mail, file share) specifies how report is delivered

E-mail delivery requires an SMTP serverExtensible delivery architecture

Can specify output format (HTML, XLS)Can deliver links as well as rendered reports

Two types of subscriptionsStandardData Driven

Standard Subscriptions

Single report sent to a fixed set of addresses

End user wants to customize his/her own report delivery

How it worksSet up by a user with ‘Manage Individual Subscriptions’ permissionUser creates a standing request to run a report at a specific time and delivered in a certain formatCan be triggered based on a schedule or snapshot generationSpecify report, execution conditions, parameters, rendering format, delivery location, etc.

In SQL Server 2005, users can subscribe to reports with User!UserID and User!Language

Data Driven Subscriptions

When to useDelivery of a report to a dynamic list of destinations with customized content for each destination

How it worksSet up by a user with ‘Manage any Subscriptions’ permissionDefine delivery query to return list of destinations and parametersSpecify delivery settings and parameter values as a static or field from delivery querySet to run according to a defined schedule or trigger from snapshot

Data driven subscriptions require SQL Sever Enterprise Edition!

Scale Out DeploymentData Sources

Flat Files,

OLE DB, ODBC

Oracle

SQL Server

DB2

ClientsReporting Services Scale Out

Deployment

Windows Server

SQL Server

Report Metadata and Cache

Failover Cluster

NLB

Report Server

Windows Server

IIS

Windows Server

SQL Server

Report Server

Windows Server

IIS

Report Server

Windows Server

IIS

Scale out requires SQL Sever Enterprise Edition!

Scale Out Setup

Run setup (files only) to install first report

server instanceRun setup (files only) to install second report server instanceUse configuration tool to create report server database and configure first report

server instanceUse configuration tool to configure second report server instanceInstall and configure load balancing functionality (NLB, switch)

Server Configuration Files

Unique per Report Server – not transferableConfiguration (including extensions) should be same per machine in scale-out deployment

Specific areas of interestReport Server database connectionReport Execution account and passwordExtension Configuration (including E-mail Delivery)

Use Configuration Tool, text editor or command line utilities to modify

File monitoring updates server settings

Code Access Security (CAS) for extensions stored in separate file

Data EncryptionWhen data source connections and credentials are stored, they are encrypted in Report Server databaseStored symmetric key encrypted with instance-based private key

In SQL Server 2005, only Windows service has encryption/decryption logicShared by all machines in scale-out deploymentRestore key when machine name, installation or Windows service account changes

Manage keys with RSKEYMGMT or Configuration Tool

Extract a copy of the encryption keyApply stored encryption keyRemove encrypted data on machine

Always backup your symmetric key!

Wrap Up

General “Care and Feeding” of your Report Server is easy!

Once initial configuration has been finished, many users can manage content themselves

Complex configurations will require planningNetwork infrastructureSecurity architectureDeployment policiesScalability requirements

SharePoint integrated mode in SP2 requires understanding of WSS management as well

ResourcesReporting Services Product Sitehttp://www.microsoft.com/sql/reporting

Technical Chats and Webcastshttp://www.microsoft.com/communities/chats/default.mspx http://www.microsoft.com/usa/webcasts/default.asp

MSDN & TechNet http://microsoft.com/msdnhttp://microsoft.com/technet

Virtual Labshttp://www.microsoft.com/technet/traincert/virtuallab/rms.mspx

Newsgroupshttp://communities2.microsoft.com/communities/newsgroups/en-us/default.aspx

Technical Community Siteshttp://www.microsoft.com/communities/default.mspx

User Groupshttp://www.microsoft.com/communities/usergroups/default.mspx

© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.

MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Appendix

Logging and Monitoring

Performance monitoringCounters for performanceReport Execution for analysis

Event log integrationCritical events and errors

Trace eventsCan trace all server activities, response times, security eventsDetail level depends on configuration setting

Server Watson support

Automating Repetitive Tasks

ExamplesDuplicate settings between serversMigrate from test to production EnvironmentChange shared data sourcesCancel running jobs

Automate web service tasks through Report Server Script Host (RS.EXE)

Visual Studio .NET not required for executionNeed to run as user with all permissions