Successfully reported this slideshow.

Sql Server 2005 Reporting Services


Published on

A practical look at the many powerful facets and Sql Server 2005 Reporting Services.

  • Be the first to comment

  • Be the first to like this

Sql Server 2005 Reporting Services

  1. 1. SQL Server 2005 Reporting Services Presenters: Jeff Benetti and Steve Schell
  2. 2. Overview <ul><li>The Reports Server </li></ul><ul><ul><li>Viewing Reports </li></ul></ul><ul><ul><li>Accessing Data Sources </li></ul></ul><ul><ul><li>Linked Reports </li></ul></ul><ul><ul><li>Configuring Report Execution and Security </li></ul></ul><ul><ul><li>Managing Report Subscriptions </li></ul></ul><ul><li>Report Development from BIDS (Visual Studio) </li></ul><ul><ul><li>SQL and MDX Queries </li></ul></ul>
  3. 3. Overview <ul><li>Report Development from BIDS (Visual Studio) [continued] </li></ul><ul><ul><li>Report Layouts </li></ul></ul><ul><ul><li>Custom Code Libraries </li></ul></ul><ul><li>Integrating Reports into Web Pages </li></ul><ul><ul><li>Report Server Web Interface </li></ul></ul><ul><ul><li>Query String Parameters </li></ul></ul><ul><li>Questions </li></ul>
  4. 4. The Reports Server
  5. 5. Viewing Reports <ul><li>SQL Server Reporting Services is designed to provide a central network location for report rendering: the Report Server. </li></ul><ul><li>The Report Server is accessed via a web browser at HTTP:// ServerName /Reports/ </li></ul>
  6. 6. Viewing Reports <ul><li>The Report Server allows reports to be organized into a folder structure similar to the Windows file system. </li></ul>
  7. 7. Viewing Reports <ul><li>The user may select available parameters to customize the report results, or hidden, default parameters may initiate when the report loads. </li></ul><ul><li>Parameters may also be tied into SQL-based System variables – including domain and username – to render user-specific reports. </li></ul>
  8. 8. Viewing Reports <ul><li>Reports may also be exported from the Report Server into the following formats: </li></ul><ul><ul><li>XML file with report data </li></ul></ul><ul><ul><li>CSV (comma delimited) </li></ul></ul><ul><ul><li>TIFF file </li></ul></ul><ul><ul><li>Acrobat PDF file </li></ul></ul><ul><ul><li>Web archive (HTML) </li></ul></ul><ul><ul><li>Excel </li></ul></ul>
  9. 9. Accessing Data Sources <ul><li>Reports access report data via “Data Sources”. </li></ul><ul><li>Data Sources are configured using a connection string utilizing the following connection types: </li></ul><ul><ul><li>Microsoft SQL Server </li></ul></ul><ul><ul><li>OLE-DB </li></ul></ul><ul><ul><li>Oracle </li></ul></ul><ul><ul><li>ODBC </li></ul></ul><ul><ul><li>XML </li></ul></ul><ul><ul><li>Microsoft SQL Server Analysis Services (SSAS Cubes) </li></ul></ul>
  10. 10. Accessing Data Sources <ul><li>Data Sources can be setup to be: </li></ul><ul><ul><li>Custom/Report-Specific or </li></ul></ul><ul><ul><li>Shared between reports via a .RDS file uploaded to the Report Server. </li></ul></ul>
  11. 11. Linked Reports <ul><li>Once a general report is loaded to the Report Server it may be used as a template for creating other “Linked Reports”. </li></ul><ul><li>Linked Reports are versions of a general report set with specific, hidden parameters. </li></ul><ul><li>They are normally used to separate reports into different security-based user groups (i.e. California regional sales reports vs. Texas regional sales reports). </li></ul><ul><li>Linked Reports can be created quickly and easily without any redevelopment. </li></ul>
  12. 12. Configuring Report Execution and Security <ul><li>Reports can be set to render on demand or according to a scheduled cache or snapshot. </li></ul><ul><ul><li>Cached and snapshot reports conserve server resources for Reports Servers with high user traffic. </li></ul></ul><ul><li>A history of report executions can also be kept for future review. </li></ul>
  13. 13. Configuring Report Execution and Security <ul><li>Report security can be set on each specific report or each Report Server folder. </li></ul><ul><li>Report security roles are set according to Active Directory User Groups or existing SQL Server Report Server database roles. </li></ul><ul><li>Users must have sufficient access to the report/folder AND the corresponding Data Source to view data within a report. </li></ul>
  14. 14. Managing Report Subscriptions <ul><li>Reports may be scheduled for delivery to network folder or email destination(s) according a “Subscription”. </li></ul><ul><li>Subscription destinations can be set explicitly or they can be data-driven (i.e. all email address for Regional Sales Managers found on the “employee” table will receive the daily Regional Sales Report). </li></ul><ul><li>Subscriptions can be shared between reports. </li></ul>
  15. 15. Managing Report Subscriptions <ul><li>Subscriptions can also deliver exported versions of reports (CVS, PDF, TIF, HTML, Excel, etc.) </li></ul>
  16. 16. Report Development from BIDS (Visual Studio)
  17. 17. SQL and MDX Queries <ul><li>All reports begin with one or more queries or stored-procedures developed off one or more data resource. </li></ul><ul><li>SQL queries and stored procedures may be used to access data from database resources. </li></ul><ul><li>MDX queries may be used to access data from OLAP cubes. </li></ul><ul><li>These queries feed data both to the main report tables AND any data-sourced parameter values. </li></ul>
  18. 18. Report Layouts <ul><li>Main report layouts may be in tabular or matrix format </li></ul><ul><ul><li>Tabular format allows multi-level groupings. </li></ul></ul><ul><ul><li>Matrix format allows cross-referencing of column and row data (Pivot-table format). </li></ul></ul>
  19. 19. Report Layouts <ul><li>Report cells may be enhanced by MDX expressions </li></ul><ul><ul><li>Report data fields may be interrelated with each other and/or other report items (report name, run date, etc). </li></ul></ul><ul><ul><li>Report properties may also be data-driven (hidden cells based on other cell content, text or background color based on cell values, etc). </li></ul></ul>
  20. 20. Report Layouts <ul><li>Grouping aggregations are automatically handled at each level based on the grouped column. </li></ul><ul><li>Reports may be hyperlinked into each other or looped back into themselves allowing parameters to be passed from one instance to the other. </li></ul><ul><li>Data fields may also be fed into charts and graphs for a more graphical presentation of the report results. </li></ul>
  21. 21. Custom Code Libraries <ul><li>In support of MDX expressions, custom procedures and functions can be coded from .NET languages (VB and C#). </li></ul><ul><li>These custom procedures can be included across multiple report definitions by way of DLL files. </li></ul>
  22. 22. Integrating Reports into Web Pages
  23. 23. Report Server Web Interface <ul><li>The Report Server also provides an .ASPX web interface accessed at HTTP:// ServerName /ReportServer/ </li></ul><ul><li>Individual reports may be hyperlinked into a webpage using this URL along with the sub-folder and report names showing in the query string, for example: </li></ul><ul><ul><li>http://ServerName/ReportServer/Pages/ReportViewer.aspx?%2fSales%2fRegional+Sales+Report&rs:Command=Render </li></ul></ul>
  24. 24. Report Server Web Interface <ul><li>This URL may also be used in an iFrame to embed the Report Server page into another webpage. </li></ul>
  25. 25. Query String Parameters <ul><li>Report-specific parameters may also be passed along the URL query string: http://ServerName/ReportServer/Pages/ReportViewer.aspx?%2fSales%2fRegional+Sales+Report&rs:Command=Render &RegionName=Texas </li></ul>
  26. 26. Query String Parameters <ul><li>Query string parameters may also be passed to configure the Report Server report viewer itself: </li></ul><ul><ul><li>To resize the report viewer window </li></ul></ul><ul><ul><li>To disable the users’ available parameters </li></ul></ul><ul><ul><li>To hide the report viewer tool bar </li></ul></ul><ul><ul><li>Example: </li></ul></ul><ul><ul><li>http://ServerName/ReportServer/Pages/ReportViewer.aspx?%2fSales%2fRegional+Sales+Report&rs:Command=Render& rc:Parameters=false </li></ul></ul>
  27. 27. Questions?
  28. 28. Thank you!