SQL: Before Disaster Strikes (Disaster Recovery) Session #4184 www.msdslug.com SQL: Before Disaster Strikes (Disaster Recovery) Session #4184 How do you plan for Disaster Recovery for your Dynamics SL? What should you do when planning, before, during and after a disaster? Be prepared because it will happen.

Hello! I am Brad Boothby Independent SL Consultant San Diego, CA 858.805.1515 brad.boothby@datanet-ca.com linkedin.com/in/bboothby San Diego, September 2016

Hello! I am Paige Rodgers Independent SL Consultant Microsoft Certified Trainer Dallas, TX 469.774.2475 paige@rodgerstx.com San Diego, September 2016

Session Agenda What is a “Disaster”? What is my SLA (Service Level Agreement)? What do I need for a SQL “Disaster”? How do I prevent \ reduce “Disasters” from occurring?

What is a “Disaster”? Data center destroyed (Hurricane, Tornado, Flood) Total Server Crash Corrupted\ damaged disk array Accidentally Dropped DB Unknown modified Proc, View or Function Deleted records

What is my SLA (Service Level Agreement)? Expectations based on severity? Data Center destroyed Hardware replacement dependent Multi site replication Server crash Replication almost no loss. Warm Stand by 2 hour online. No data loss over 2 hours.

What is my SLA (Service Level Agreement)? Potential Data loss Immediate notification Newly entered Old data Delayed notification How long ago was it entered?

What do I need for a SQL “Disaster”? Database Engine (SSDE) Password for protected backups User DB SQL Backups System DB Backups Know version of SQL SSL certificate store and password Decryption keys and passwords SharePoint Backups should be made with website down.

What do I need for a SQL “Disaster”? Database Engine (SSDE) Help full Original folder structure Service accounts and passwords SQL user names and passwords Analysis Services (SSAS) AS DB Backups Encryption password Hashed users and passwords\ export usefull.

What do I need for a SQL “Disaster”? Reporting Services (SSRS) Backup relational DBs Encryption Keys and Password Configuration Files Rsreportserver.config Rssvrpolicy.config Rsmgrpolicy.config Reportingservicesservice.exe.config Web.config for both the Report Server and Report Manager ASP.NET applications Machine.config for ASP.NET

What do I need for a SQL “Disaster”? Reporting Services (SSRS) Data files Report files (.rdl) Shared Data files (.rds) Data View (.dv) Data Source (.ds) Report model (.msdl) Report project (.rptproj) Report solution (.sln)

What do I need for a SQL “Disaster”? Reporting Services (SSRS) Script files (.rss) Custom extensions and assemblies Integrated Services (SSIS) MSDB (stored) System MSDB database must be backed up Configuration files stored in file system

What do I need for a SQL “Disaster”? Integrated Services (SSIS) File system (stored) MsDtsSrvr.ini.xml default Integration Service service configuration file List of folders that are monitored Any other folders where packages are stored

How do I prevent \ reduce “Disasters” from occurring? DML Triggers Do not allow “Delete from” with out where DDL Triggers Prevent changing of SQL objects Prevent accidental “Drop Database” Prevent accidental “Alter Proc\ view”

Demo Triggers

Files on Download DDL_Database_Drop_RollBack DDL_Procedure_Alter_RollBack DDL_Procedure_Drop_RollBack DDL_Table_Drop_RollBack DDL_Views_Drop_RollBack DML snote_Trig_del

Thanks!! Any questions now? See Hello slides. If not, you can always contact me later: See Hello slides. San Diego, September 2016

Next Steps Session Next Steps Please fill out: Why fill them out? Any downloads? Please fill out: A session evaluation online A session big idea card Why fill them out? To make our conferences better To Win Prizes!! Drawings held: Friday, Sept 30th Friday, Oct 7th San Diego, September 2016