WHAT’S NEW IN sql Server 2012 REPORTING SERVICES

1. WHAT’S NEW IN sql Server 2012 REPORTING SERVICES SQL11UPD06-DECK-03 Updated: 06-Nov-2011

2. REPORTING SERVICES 2012 OVERVIEW

3. What’s new in SQL server 2012 reporting services • Empower users with a new visual design experience (Power View) • Increase productivity with user-defined data alerts • Increase performance and improve administration within SharePoint • SharePoint shared service application • Built-in scale-out for Reporting Services service applications • SharePoint cross-farm reporting • Integrated backup and recovery, ULS logging, PowerShell, etc. • Visual Studio 2010 designers • Excel renderer for Excel 2007-2010 • Word renderer for Word 2007-2010

4. Data alerts • Data alerts can be defined on the report feed(s) • Name • Intuitive alert rules based on conditions (AND and OR) • Scheduling settings • Advanced: Start/End dates • Email address, Subject and Description • Can only be based on reports that use data sources with stored credentials • Alerts can be managed by users and administrators • View status, Edit, Delete, Run • Only available in SharePoint integrated mode

5. SharePoint Integrated Mode • Shared Service Application • Maximum set of SharePoint IT management capability is enabled • Lower TCO on IT who can now leverage existing SharePoint skillset and experience • All configuration is now simplified and easier, use: • Central Admin • PowerShell • Leverages SharePoint’s in-built scale capability • File types are understood • Context menus to manage reports, configure alerts, etc. are available • BISM Connection File content type is installed • Stores connection information to a tabular BI Semantic Model (PowerPivot file or hosted tabular model) • Users can launch Power View from this document • It can also be used in a connection string to access the model

6. Introducing Power view

7. Sql server 2012 power view • Power View is an interactive data exploration, visualization, and presentation experience • Highly visual design experience • Rich meta-driven interactivity • Presentation-ready at all times • Provides intuitive ad-hoc reporting for business users such as data analysts, business decision makers, and information workers

8. Power view system requirements • A Power View report must be based on a deployed tabular BI Semantic Model • PowerPivot workbook in a SharePoint library • Tabular model hosted on a tabular instance of Analysis Services • DAX Tabular Queries are used to query the model • Ordinarily, the tabular BI Semantic Model needs to be optimized for the Power View experience • Server(s): • SharePoint Server 2010 SP1 • SQL Server 2012 Reporting Services Add-in for SharePoint • Client: • Supported browsers: • Windows Vista: IE7 32-bit, FireFox 4 • Windows 7: IE8 32-bit, IE9 32-bit, FireFox 4, Safari • Note the InPrivate browsing feature of IE is not supported • Silverlight 4 (Silverlight 5 by RTM)

9. Creating and designing Power View Reports • Users create a new Power View report (.rdlx) from: • A BISM Connection File (.bism) • An Excel document (.xlsx) in the PowerPivot Gallery (in Gallery view) • A reporting services (.rsds) shared data source based on a tabular BI Semantic Model • Reports may be saved to SharePoint libraries • Clicking the report will open it • The report opens in Preview mode • If the user has permission, they can switch to Edit mode • The design experience consists of: • Canvas • Home and Insert ribbons • Field List • Field selection • Layout selection • Filter area • Title • The report may be viewed in Preview or Full Screen mode • Visualizations can be added to the canvas and then configured using the Layout Selection

10. SQL AZURE REPORTING

11. SQL Azure Reporting • SQL Azure Reporting is • SQL Server Reporting Services technology delivered as a service on the Windows Azure Platform • Available for testing via public CTP3 • Ideal for operational reporting against SQL Azure data • Enterprise-ready with automatic support for HA • Designed to scale elastically with demand • Get started quickly • Provision report server via Windows Azure Management Portal • Build reports with Reporting Services Report Designer • Deploy reports to report server • Render reports with Visual Studio ReportViewercontrols

12. SQL Azure Reporting • Use familiar technologies • Visual Studio Report Designer • RDL (Report Definition Language) • Report items and visualizations • Report Server Web Service / URL access • Visual Studio ReportViewerControl • Identity and access control • SQL authentication supported (no support for integrated authentication) • Admin user configured during provisioning • Admin user has all rights on server, use for administration only • Provision users using portal or web service • Add users to appropriate item (Browser, Publisher) and system roles (User, Admin) • Grant item-level permissions to folders or reports • Differences in comparison to Reporting Services • Focus on logical vs. physical administration • Report catalog and temporary database automatically provisioned • Windows Azure Management Portal replaces Report manager • SSL Required • SQL Azure data sources only • Unsupported Reporting Services features • Report Builder • Subscriptions, schedules, caching • Custom extensions • Report models • External images