2. Microsoft Dynamics NAV Dynamics NAV 2016 one Azure SQL Dmitry Chadayev Microsoft

3. Microsoft Dynamics NAV

6. Infrastructure (as a Service) Storage Servers Networking O/S Middleware Virtualization Database Applications SQL Server Managed by Azure You scale, make resilient & manage You manage Platform (as a Service) Scale, Resilience and management by Azure Storage Servers Networking O/S Middleware Virtualization Applications SQL Server Database On Premises You scale, make resilient and manage Storage Servers Networking O/S Middleware Virtualization Database Applications SQL Server

8. 8 Small databases with a light transactional workload. Predictable hourly transaction rates. Performance level: Basic Designed for mission- critical databases. Offers the highest level of performance and access to advanced business continuity features. Predictable per second transaction rates. Performance levels: P1, P2, P4, P6 Service Level Complex Support Custom Solutions The go-to option for most applications. Mid-level performance to support multiple concurrent transactions. Predictable per minute transaction rates. Performance levels: S0, S1, S2, S3 More information BASIC STANDARD PREMIUM

9. Across the service tiers, each performance level is assigned a defined level of throughput for a streamlined experience Defined using the Database Throughput Unit (DTU) which represents database power and replaces hardware specs Performanc e Tiers Measure of power % CPU % read % write % memory Basic — 5 DTU S0 — 10 DTU S2 — 20 DTU S3 — 50 DTU S4 — 100 DTU P1 — 125 DTU P2 — 250 DTU P4 — 500 DTU … DTU is defined by the bounding box for the resources required by a database workload and measures power across the performance levels. Compute Writes Reads Memory

10. Geo-Restore Standard Geo- Replication Point In Time Restore Active Geo- Replication Provides the default recovery option when database is unavailable because of an incident in the region where your database is hosted. Relies on database backups in geo-redundant Azure storage. ERT (Estimated Recovery Time) < 12 h RPO (Recovery Point Objective) < 1 h Designed for applications that have more aggressive recovery requirements than Geo-Restore can offer. When the primary database fails you can initiate failover to a non-readable secondary database stored in the DR (disaster recovery) paired region. ERT < 30 sec ; RPO < 5 sec More information Designed to return your database to an earlier point in time. Uses the database backups, incremental backups and transaction log backups that the service automatically maintains for every user database. Available only for Premium databases for write-intensive applications with the most aggressive recovery requirements. You can create and initiate failover to up to four readable secondaries on servers in different regions. ERT < 30 sec ; RPO < 5 sec Business continuity is about designing, deploying and running your application in a way that it is resilient to planned or unplanned disruptive events that result in permanent or temporary loss of the application’s ability to conduct its business function.

11. Replicas Enable Database High Availability Reads are completed at the primary Writes are replicated to secondaries DB Single Logical Database Majority quorum up to 4 replicas Transparent automatic failover Uptime SLA of 99.99% Zero user or admin config Write Ack Read Write Ack P P SS T-SQL Query P P S S

12. Logins/UsersDatabaseServerSubscription Logical Server 1 masterLoginsUserDB1Users Logical Server 2 …

16. Cost Administration Service level agreement (SLA) and compliance Business continuity Billed hourly at a fixed rate, instead of having to pay for a SQL license upfront Eliminates hardware costs, near-zero administrative costs Built-in support for high availability, automatic backups, data protection and fault tolerance The database software is automatically patched, and upgraded by Microsoft Azure Database-level availability SLA of 99.99% Azure certifications : ISO, HIPAA BAA, EU Model Clause Multiple built-in business continuity features Point in Time Restore, Geo-Restore, and Geo- Replication

17. Predictable performance and scalability Setup and administration Simple migration path Familiar SQL Server tools and APIs for developers and admins Adjust performance and scale without downtime Make use of monitoring and troubleshooting features for index tuning and queries optimization Focus on rapid application development, rather than managing the infrastructure Azure takes care of the physical resources of the underlying SQL Server instance Upload and manage your existing database via Azure Portal, SSMS or an API Connect securely from Microsoft Dynamics NAV 2016 Access via REST API, PowerShell, Azure Portal, SQL Server Management Studio Nearly complete compatibility with the SQL Server engine

18. 6 How Do I Videos https://mbs.microsoft.com/partnersource/northamerica/readiness- training/readiness-training-news/VideoSeriesNAVPerformanceTesting

19. O365 Auth. User/Password SP BI

21. Learn more http://aka.ms/NAVGetRea dy

26. SQL DB V12