Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
SQL Server 2016 Reporting Services Cookbook

You're reading from   SQL Server 2016 Reporting Services Cookbook Your one-stop guide to operational reporting and mobile dashboards using SSRS 2016

Arrow left icon
Product type Paperback
Published in Nov 2016
Publisher Packt
ISBN-13 9781786461810
Length 596 pages
Edition 1st Edition
Languages
Arrow right icon
Authors (2):
Arrow left icon
Robert Cain Robert Cain
Author Profile Icon Robert Cain
Robert Cain
Dinesh Priyankara Dinesh Priyankara
Author Profile Icon Dinesh Priyankara
Dinesh Priyankara
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Getting It Ready – Configuring Reporting Services FREE CHAPTER 2. Authoring Reports with SQL Server Data Tools 3. Advanced Report Authoring with SQL Server Data Tools 4. Authoring Reports with Report Builder 5. Improving User Experience – New Designing and Visualization Enhancements 6. Authoring Reports with the Mobile Report Publisher 7. Consuming Reports – Report Access Enhancement 8. Reporting Solutions for BI – Integration 9. SharePoint Integration 10. Administering and Managing Reporting Services 11. Securing Reports in Reporting Services 12. Custom Programming and Integration to .NET Applications

Backing up Reporting Services


Things can go wrong unnoticed. An unexpected hardware failure or software failure can damage Reporting Services environment, making it unavailable for users. Database Administrator or Reporting Services Administrator must work on it for fixing or recovering the environment and bring Reporting Services up and running as quickly as possible.

How do we recover if something has damaged the Reporting Services? In order to recover, you need to make sure that you have copies of all required components such as .rdl files, databases, modified configuration files, and encryption keys if used. Do we need a strategy for keeping these components?

Let us see what copies of components we need to keep and how they can easily use for recovering.

Getting ready

Deciding the recovery plan is based on two factors called RTO and RPO. Recovery Time Objective (RTO) refers how long can recover take and RPO; how much data is it acceptable to lost, must be discussed with business users and...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image