1. STRYK System Improvement

2. MS Dynamics NAV (Navision) since 1997 MS SQL Server since 2003 100% Focus on „NAV/SQL Performance Optimization“ STRYK System Improvement (since 2006) Worldwide support of MS Dynamics Partners & Customers Microsoft Most Valuable Professional (MVP MS Dynamics NAV) Book:“NAV/SQL Performance Field Guide” (ISBN 978-3-8370-1442-6) Software:“NAV/SQL Performance Toolbox” http://www.stryk.info/toolbox.html http://www.stryk.info/toolbox.html Blog:“NAV/SQL Performance – My Two Cents” http://dynamicsuser.net/blogs/stryk/ http://dynamicsuser.net/blogs/stryk/ Contact:contact@stryk.infocontact@stryk.info http://www.stryk.info Introduction Jörg Stryk

3. NAV/SQL High Availability: High Availability with NAV and SQL Server Some “Inspirations” Abstract: With increasing transaction volumes processed by NAV customers the need for HA solutions is also growing. This session will explain some available HA solutions with NAV and SQL as there are e.g. “Transaction Log-Shipping” and “Mirroring”, but also in addition with using “Database Snapshots”. The advantages and disadvantages of the several solutions are discussed to inspire NAV partners to implement the appropriate scenarios at their customer’s sites. Agenda

4. Two Big Questions What is the maximum acceptable Data-Loss? What is the maximum acceptable Server-Down-Time?

5. Off Topic Backup Strategies (“Cold Stand-By”) 18:00…08:0009:0010:0011:0012:0013:0014:0015:0016:0017:0018:00 Full Diff Full Log

6. Window Failover Cluster (“Hot Stand-By”) Off Topic Active NodePassive Node Failover Storage = „Single Point of Failure“ „Heartbeat“ Active Node Passive Node

7. Warm-Standby Solutions Transaction Log Shipping Database Mirroring Database Snapshots

8. Transaction Log Shipping Warm-Standby Solutions Failover NAV Standard NAV Main ServerStandby Server NAVNAV (STANDBY) Client PC TRN Monitor

9. Database Mirroring Warm-Standby Solutions Failover NAVStandard NAV Principal ServerMirror Server NAVNAV (NO RECOVERY) Client PC LSN Witness

10. Synchronous vs. Asynchronous Mirroring Warm-Standby Solutions Principal ServerMirror Server Client PC LSN COMMIT aka „High Safety Mirroring“ With Witness: „High Availability Mode“ No Witness: „High Protection Mode“ Witness

11. Synchronous vs. Asynchronous Mirroring Warm-Standby Solutions Principal ServerMirror Server Client PC LSN COMMIT aka „High Performance Mirroring“

12. Database Snapshots Additional (?) SQL Server (Enterprise) NAV NAV_SNAPSHOT (read only) Client PC Snapshot Read/Write Read Only Data „Freeze“

13. Demo

14. Overview OptionEditionFailoverWitnessData-LossDown-TimePerformanceMultiple Mirrors Connect to Mirror Costs Failover ClusterOS: EEAuton/aminimal high(Yes)n/a$$$ Mirroring (Async)SQL: EEManualNosmallmediumhighNo $$ Mirroring (Sync)All(Auto)Yesminimalmedium No $ Log ShippingAll(Auto)Yesmedium Yes(Read Only)$ BackupsAllManualNomedium+maximummediumYesn/a$ DB SnapshotsSQL: EEn/a Read Only$$

15. HA & Failover Scenario Failover NAV #1 Standard NAV Reporting NAV Principal ServerMirror Server NAVNAV (NO RECOVERY) NAV_SNAP (read only) Snapshot Backup BAK/TRN SQL Backup Client PC Mirroring Standby Server NAV (STANDBY) Log Shipping Failover NAV #2

16. Challenges What is the maximum acceptable Data-Loss? What is the maximum acceptable Server-Down-Time? Transferring Logins Notifications and Reactions Time to get Standby-System online Time to recover Backup Time to get Primary-System online Who/What/When Re-Routing Clients/Service Tier(s) Weekend/Holiday Interfaces Licensing

17. SQL Server 2012 “Denali” The Future HADRON = High Availability & Disaster Recovery - Always ON Querying the Mirror (= Replica) Multiple Replica Database Availability Groups Mirroring more than 10 databases Faster Recovery Automatic Failover http://www.microsoft.com/sqlserver/en/us/product-info/future-editions.aspx

18. Q & A Questions?Thanks for your attention!