Book Image

SQL Server 2016 Reporting Services Cookbook

By : Dinesh Priyankara, Robert Cain
Book Image

SQL Server 2016 Reporting Services Cookbook

By: Dinesh Priyankara, Robert Cain

Overview of this book

Microsoft SQL Server 2016 Reporting Services comes with many new features. It offers different types of reporting such as Production, Ad-hoc, Dashboard, Mash-up, and Analytical. SQL Server 2016 also has a surfeit of new features including Mobile Reporting, and Power BI integration. This book contains recipes that explore the new and advanced features added to SQL Server 2016. The first few chapters cover recipes on configuring components and how to explore these new features. You’ll learn to build your own reporting solution with data tools and report builder, along with learning techniques to create visually appealing reports. This book also has recipes for enhanced mobile reporting solutions, accessing these solutions effectively, and delivering interactive business intelligence solutions. Towards the end of the book, you’ll get to grips with running reporting services in SharePoint integrated mode and be able to administer, monitor, and secure your reporting solution. This book covers about the new offerings of Microsoft SQL Server 2016 Reporting Services in comprehensive detail and uses examples of real-world problem-solving business scenarios.
Table of Contents (18 chapters)
SQL Server 2016 Reporting Services Cookbook
Credits
About the Authors
About the Reviewers
www.Packtpub.com
Preface

Caching the report


When a request is sent by a user for a report to Reporting Services, with default configurations, it needs to extract data from the related source, process and then render. Depending on the volume of data, the complexity of the process and the time it takes for forming the output, it might take few seconds or it might take hours for rendering. If it takes a longer time than expected, it is considered as a performance issue.

Caching improves the performance. Reporting Services can cache the report with initial execution based on the instructions given by us and use the cached copy for stratifying next requests on the same report with the same parameter values if it is a parameterized report. Caching does not help with the first request. For an example, if it takes 5 minutes for opening the report, the next request for the same will be treated from the cache, hence request will be satisfied within a few seconds.

Getting ready

If you are going to enable caching for a report...