Professional Documents
Culture Documents
Agenda
Introduction Introduction
What is SQL Reporting Services ? Basic architecture Components of SRS What does it do?
Demonstrations Demonstrations
Product features Basic report with drill-down Add parameters to the report Report Model Designer Ad-Hoc Report Builder Other features (time-permitting)
Development Tools
Integration Services
ETL
SQL Server
Relational Engine
Demo
SQL Server Reporting Services UI
Security
Report Processing
Floating Headers
Similar to Excel Splitters On Table and matrix
Report Designer
Integrated into Visual Studio 2005
Supports all languages (C#, VB, J#)
Drag & drop features Use tables, charts, matrices, etc. to display data Specify grouping, sorting, filtering, etc. Style the report by specifying fonts, colors, etc. Use expressions to change style dynamically based on data values
Demo
VS.NET Report Designer Build basic report with drill-down Add/Change styles Deploy report Access from Report Server
Local Mode
For processing and viewing reports without connecting to a Report Server
Data is retrieved and report is processed on server, only resulting output is returned to client Drilldown, drillthrough, etc. are automatically handled Export to all formats supported by Report Server, including Excel, PDF and MHTML
Your Application
Local Mode
Host Application
Supplies report definition and data for the report Implements parameter UI Connects to databases and executes queries Supplies data as ADO.NET DataTables or as a collection of business objects
Designed to be secure
Code embedded in the report cannot access file system or network without explicit coding
Same engine as SQL Server 2005 Reporting Services Supports printing and export to Excel or PDF
Demo
ReportViewer control Local and Server mode
Demo
Demo
Report Manager Management options
Report Caching
Execution Sessions
Automatically created for each report execution Keeps consistency between server round trips (images, paging, exporting) Session timeout set in server properties
Cache Snapshots
On-demand reports can be cached between users Cache index is based on parameter values Cache valid for a specified time after execution or cleared on schedule Limitations User-specific expressions (User ID, Language), stored credentials
History Snapshots
Multiple instances of report snapshots for archiving, auditing purposes Stored independently of data source, report definition System and report-specific retention policy
Scheduling
Management events can be scheduled on the report server
Caching, Subscriptions, History
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 server Extensible delivery architecture
Standard Subscriptions
Single report sent to a fixed set of addresses
End user wants to customize his/her own report delivery
How it works
Set up by a user with Manage Individual Subscriptions permission User creates a standing request to run a report at a specific time and delivered in a certain format Can be triggered based on a schedule or snapshot generation Specify report, execution conditions, parameters, rendering format, delivery location, etc.
In SQL Server 2005, users can subscribe to reports with User!UserID and User!Language
How it works
Set up by a user with Manage any Subscriptions permission Define delivery query to return list of destinations and parameters Specify delivery settings and parameter values as a static or field from delivery query Set to run according to a defined schedule or trigger from snapshot
SQL 2005 Reporting Services supports use of SQL Server 2000 relational database
Caveat: Setup upgrades all components in default instance