Help, I need to migrate my On Premise Database to Azure, which Database Tier do I have to choose from (DataSaturday NL 2019 Erwin de Kreuk / Ahmed Mansour)
- 2. Sponsored by
- 3. A G E N D A • Azure SQL deployment options • Data Migration Assistant • Data Migration Service • Questions
- 4. Azure SQL Database The developer’s intelligent cloud database service
- 5. Azure SQL Database deployment option Azure SQL Database Database-scoped deployment option with predictable workload performance Shared resource model optimized for greater efficiency of multi-tenant applications Best for apps that require resource guarantee at database level Best for SaaS apps with multiple databases that can share resources at database level, achieving better cost efficiency Best for modernization at scale with low friction and effort Elastic PoolSingle Managed Instance Instance-scoped deployment option with high compatibility with SQL Server and full PaaS benefits ServiceTiers
- 6. Flexible compute & storage options Pre-packaged, bundled unit that represents the database power Designed for predictable performance, but somewhat inflexible and limited in options DTU sizing offers simplicity of choice Storage Compute Storage Compute vCore model Independent scalability DTU model Simple, preconfigured This model allows you to independently choose compute and storage resources. It also allows you to use Azure Hybrid Benefit for SQL Server to gain cost savings. Best for customers who value flexibility; control and transparency
- 7. Basic Standard Premium Target workload Development and production Development and production Development and production Uptime SLA 99.99% 99.99% 99.99% Backup retention 7 days 35 days 35 days CPU Low Low, Medium, High Medium, High IO throughput ( approximate) 2.5 IOPs per DTU 2.5 IOPs per DTU 48 IOPs per DTU IO latency ( approximate ) 5 ms (read), 10 ms (write) 5 ms (read), 10 ms (write) 2 ms(read/write) Columnstore indexing N/A S3 and above Supported In-memory OLTP N/A N/A Supported Azure SQL DB DTU Model
- 8. Easier to right-size the destination environment by removing the guesswork of DTUs Azure SQL DB vCores Model 2 403 2 Number of vCores (Gen 5) On-premises … 24 64 80 Gen 4 Gen 5 Hardware Intel E5-2673 v3 (Haswell) 2.4 GHz processors vCore = 1 PP (physical core) Intel E5-2673 v4 (Broadwell) 2.3 GHz processors, fast eNVM SSD vCore=1 LP (hyper-thread) Performance levels 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 16, 24 vCores 2, 4, 6, 10, 12, 14, 16, 18, 20, 24, 32, 40, 80 vCores Memory 7 GB per vCore 5.1 GB per vCore Storage 5 GB to 4 TB with 1 GB increments. 5 GB to 4 TB with 1GB increments. Max data IOPS 500 IOPS per vCore 500 IOPS per vCore Max log rate (MBps) 7,5 per 2vCores 3,75 per 2vCores Hybrid Benefit Yes Yes
- 9. Azure SQL DB vCores Model 2 403 2 Number of vCores (Gen 5) On-premises … 24 64 80 General Purpose Business Critical Target workload For applications with typically loads. Mixed of Reads/Writes For applications that require the highest throughput and lowest IO latency. Storage Premium blob storage Local SSD storage. IO Latency ( approximate) 5-7 ms (write) 5-10 ms (read) 1-2 ms (write) 1-2 ms (read) Max data IOPS 500 IOPS per vCore 5000 IOPS per vCore In Memory Not Supported Supported Replicas 2 Read Replicas 3 Read Replicas, 1 read-scale replica
- 10. Take an inventory of on-premises licenses to determine potential for conversion Convert on-premises cores to vCores to maximize value of investments 1 Standard license core = 1 General Purpose or Hyperscale core 1 Enterprise license core = 1 Business Critical core 1 Enterprise license core = 4 General Purpose or Hyperscale cores (virtualization benefit) Azure Hybrid Benefit for SQL Server License trade-in values General purpose or Hyperscale vCore 4x General purpose or Hyperscale vCores Business critical vCore SQL Server cores with SA license vCores on Azure SQL Database SQL Server Enterprise Edition SQL Server Standard Edition
- 11. The growing need for serverless databases
- 12. Why serverless Compute requirements for new apps may be unknown Developers struggle to provide sufficient capacity and resources to support apps Managing unpredictable and intermittent workloads is costly and time-consuming Businesses struggle to ensure that database provisioning consistently aligns with workload requirements ?
- 13. Optimize price to performance with per-second billing Compute resources scale dynamically up or down based on workload requirements Configure minimum and maximum vCores to define the range of available compute capacity Use auto-pause delay to define the time period the dataset must be inactive before pausing Pay for compute based on the vCores and memory used per second, with lowest billing based on configured vCore minimum Min vcores CPU usage Inactive Paused Max vcores Vcores used Vcores billed
- 14. On-demand flexible scale Operate at the true rhythm of your business Fully managed & intelligent Focus on your applications, not your infrastructure Cost-effective Pay for performance. Period. Adapts compute resources to the workload without sacrificing performance Automatically pauses and resumes Fully-managed and intelligent database service Built-in 99.99% availability Pay only for compute resources you consume, on a per-second basis Further optimize costs with configurable compute thresholds Best for unpredictable and intermittent workloads on single databases, such as: Dev/test E-commerceLine of Business
- 15. Workloads with unpredictable and intermittent usage patterns or performance requirements Workloads where the requirements are unknown and you can delegate compute sizing to the service Common scenarios Scale up or down to meet workload requirements, instead of pre-provisioning Bill on a per-second basis Optimize compute provisioning and billing for your workload Serverless databases… Workloads with regular and substantial compute utilization Multiple databases with bursty usage patterns that can be consolidated into a single server and use elastic pools for better price optimization Common scenarios Provision compute resources upfront Bill on an hourly basis Databases with provisioned compute…
- 16. Scaling multiple databases across shared resources with elastic pools
- 17. Elastic databases in elastic database pools Pooled resources are used by many databases Standard elastic database pools provide 50-3000 database throughput units (DTUs) for up to 500 databases Max eDTUs per database can be set if available based on utilization by other database in the pool Databases remain online throughout Monitoring and alerting available on both pools and databases Model Based on DTU or on vCore Azure SQL DB eDTU Model DTUs Max per-database burst level 1,200800400200
- 18. S0 S1 S2 S3
- 19. S0 S1 S2 S3
- 21. Pools automatically scale performance and storage capacity for elastic databases— anytime, anywhere Control the performance assigned to a pool, add or remove elastic databases on demand, and define performance of elastic databases without effecting overall pool cost Don’t worry about managing usage needs of individual databases Auto-scaling you control with Elastic Database Elastic pools Shares elastic Database Transaction Units (eDTUs) across many databases Customer 1 Customer NCustomer 3Customer 2 Elastic Database auto-scales eDTUs as needed
- 22. ELASTIC DATABASE POOLS Buy a fixed number of eDTUs, share compute across many databases Elastic database pool service tiers Basic Standard Premium Auto-scale up to 5 eDTUs per database Auto-scale up to 3000 eDTUs per database Auto-scale up to 4000 eDTUs per database Customer 1 Customer NCustomer 3Customer 2 …
- 23. Azure SQL Database Managed Instance
- 24. Who is Managed Instance for? Customers looking to migrate a large number of apps from on-premise or IaaS, self-built or ISV provided, with as low migration effort as possible & cost being a crucial factor Based on the vCore model (Gen4 and Gen5) SQL
- 25. Isolation and connectivity of Managed Instance
- 27. Simplicity The DTU-based model and the simplicity it offers customers who want a pre-configured solution Flexibility: The vCore-based model reflects our commitment to customer choice and to simplify the hybrid benefit for customers migrating from on- premises Customers pay for: Service tier + number of vCores Type and amount of data storage Number of IO Backup storage (RA-GRS) Flexible compute, storage & performance options Service tier General purpose Business critical Hyperscale Best for Most budget-oriented workloads Critical business applications with high IO requirements. VLDB OLTP and HTAP workloads with highly scalable storage and read-scale requirements Deployment option Single / Elastic Pools Managed Instance Single / Elastic Pools Managed Instance Single Compute tiers Gen4: 1 to 24 vCore Gen5: 2 to 80 vCore Gen4: 4 to 24 vCore Gen5: 4 to 80 vCore Gen4: 1 to 24 vCore Gen5: 2 to 80 vCore Gen4: 4 to 24 vCore Gen5: 4 to 80 vCore Gen4: 1 to 24 vCore Gen5: 2 to 80 vCore Storage Premium remote Local SSD Local SSD Cache 32GB – 8TB per instance 32GB – 8TB per instance 32GB – 4TB per instance 32GB – 8TB per instance Scale from 5GB to 100TB of storage in 1GB increments In-Memory Not supported Supported Not supported Read-write IO ~2ms for all data access <0.5ms for all data access <0.5ms for hot data access ~2ms otherwise Availability 2 read replicas 3 replicas, 1 read-scale replica, zone- redundant HA Primary read/write replica + up to 4 read replicas Backups RA-GRS, 7-35 days (7 days by default) RA-GRS, 7-35 days (7 days by default) LRS, ZRS, RA-GRS, 7-35 days (7 days by default) https://azure.microsoft.com/en-us/pricing/details/sql-database/
- 28. Pay only for what you need Business continuity and data protection: A spectrum of business-continuity features across tiers lets you dial up control over data recovery and failover Familiar and fully-managed: Near-complete SQL Server compatibility and unprecedented efficiencies as your applications scale with a near-zero maintenance service and a variety of familiar management tools and programmatic APIs Elastic scale and performance: Three service tiers within DTU-based model, and two tiers within vCore-based model let you scale up and down based on throughput needs, and offer better resource isolation and an improved billing experience DTUs vCores Basic Standard Premium General Purpose Business Critical Hyperscale Small databases particularly those in development phases General purpose databases with moderate performance requirements Mission-critical databases with high performance and high-availability requirements Data applications with basic IO and basic availability requirements Business critical data applications with fast IO and high availability requirements VLDB OLTP and HTAP workloads with highly scalable storage and read- scale requirements
- 29. © Microsoft Corporation Azure Current service tier Target service tier Migration type User actions Standard General purpose Lateral Can migrate in any order, but need to ensure appropriate vCore sizing* Premium Business critical Lateral Can migrate in any order, but need to ensure appropriate vCore sizing* Standard Business critical Upgrade Must migrate secondary first Business critical Standard Downgrade Must migrate primary first Premium General purpose Downgrade Must migrate primary first General purpose Premium Upgrade Must migrate secondary first Business critical General purpose Downgrade Must migrate primary first General purpose Business critical Upgrade Must migrate secondary first Migrate from DTU to vCore
- 31. DEMO
- 32. © Microsoft Corporation Azure
- 35. Azure SQL DB Upgrade Readiness
- 37. © Microsoft Corporation Azure Migrate
- 38. © Microsoft Corporation Database migrations Migrate SQL Server to Azure SQL Database for best TCO Migrate open source databases to fully managed MySQL and PostgreSQL services in Azure Migrate any NoSQL database to Azure Cosmos DB for global distribution Azure Database Migration Service http://aka.ms/get-dms Database Migration Guide http://aka.ms/datamigration Microsoft Azure Other clouds On-Premises SQL Server MySQL PostgreSQL NoSQL Azure SQL DB Azure Database for MySQL Azure Database for PostgreSQL Azure Cosmos DB
- 40. Azure Database Migration Service On-premises network Subnet used for DMS On-PremiseCustomer SubscriptionMicrosoft Subscription Azure Storage Account Service Bus Queue DMS Resource Provider CLI commands PowerShell Virtual Machine Azure Portal My M y
- 41. Choice of tools for every stage and every requirement Azure security and management (security, backup, monitoring, cost management) Azure Database Migration Service Azure Site Recovery Azure Data Box Assess Migrate Optimize Data Migration Assistant Azure Migrate SQL Server Migration Assistant Microsoft Partners
- 42. And there’re more database providers
- 43. © Microsoft Corporation Managed community MySQL, PostgreSQL, and MariaDB Scale in seconds with built-in high availability Secure and compliantLanguages and frameworks of your choice Industry-leading global reach Azure Database Services for MYSQL, POSTGRESQL, and MARIADB Easy lift and shift Enterprise ready My More choices and full integration into Azure’s ecosystem and services
- 44. @ https:// .com
- 46. @ https:// .com