Tips & Tricks For The Success With Azure SQL Managed Instance
Tips & Tricks For The Success With Azure SQL Managed Instance
Powered by
Powered by
Niko Neugebauer
Product Manager @ Microsoft
Niko Neugebauer
• A Senior Program Manager for SQLMI at Microsoft, in his
previous roles for over 20 years he helped customers
successfully build, migrate and optimize Microsoft Data
solutions in OLTP & OLAP markets.
Agenda
• Intro
• Backups from SQL MI to SQL Server 2022
• Hybrid Link
• Performance
• Fast Provisioning
• Start/Stop
• ADLS Virtualization
• License-free Geo-Dr
Azure SQL
The family of SQL cloud to edge databases
No
No
©Microsoft Corporation
Service tiers – Deployment options
Hardware options
General purpose Business critical
Intel Broadwell CPU
Standard
80 vCores/5.1Gb per vCore
Workloads that require low latency,
Most business workloads fast recovery, and a readable
secondary Premium-series (Intel Ice Lake CPU)
Premium 80 vCores/7 Gb per vCore
Memory optimized –
64 vCores/13.6 per vCore
Resource limits
• Memory
• Max Log Size
• I/O throughput and latency
• Size of Tempdb
• Max concurrent workers
• Backup Retention
SQL MI New HW Generations
• CPU: Intel Broadwell, Skylake and • CPU: Latest 3rd Gen Intel 8370C • CPU: Latest 3rd Gen Intel 8370C
Cascade Lake, 2.3-2.5 GHz (Ice Lake), 2.8 GHz (Ice Lake), 2.8 GHz
• vCore range: 4 – 80 • vCore range: 4 – 80 • vCore range: 4 - 64
Operates on the Provides maximum Fully-managed Secures data at New! Enables SQL
latest / compatibility with service optimized compute and Server running
“evergreen” SQL Server on-prem for DBA networking levels anywhere to get
version of SQL for low-cost app productivity * connected to Azure for
modernization auto-DR, read scale, and
online migration
scenarios
* projected ROI 230% over 3 years according to Forrester Total Economic Impact study
Evergreen version of SQL
Geo-replicated automatic-backups with built-in point-in-time restore and configurable short and
long-time retention
Built-in compliance
1 Savingsbased on eight vCore Managed Instance Business Critical in East US Region, running 730 hours per month. Savings are calculated from full price (license included) against base rate (applying Azure Hybrid Benefit for SQL Server), which excludes
Software Assurance cost for SQL Server Enterprise edition, which may vary based on EA agreement. Actual savings may vary based on region, instance size and performance tier. Prices as of May 2018, subject to change.
2 Savings based on eight vCore SQL Database Managed Instance Business Critical in West 2 US Region, running 730 hours per month. Savings are calculated from on demand full price (license included) against base rate with Azure Hybrid Benefit plus 3-
year reserved capacity commitment. Savings excludes Software Assurance cost for SQL Server Enterprise edition, which may vary based on EA agreement. Actual savings may vary based on region, instance size and performance tier. Prices as of May 2018,
subject to change.
Azure Dev/Test pricing
25 28
25
20
19
15
17
10
5 8
0
2018 2019 2020 2021 2022
Delivered
30
25 28
25
20
19
15
17
10
5 8
0
2018 2019 2020 2021 2022
Powered by
MI Link
BACKUP DATABASE
RESTORE DATABASE MyDB failover
FROM URL = … TO URL = …
Azure Storage WITH COPY_ONLY
✓ Standard-series HW
NOTE:
• Migrate on-prem OLAP into Azure with the most reuse of the existing
setup
• Without complex polybase setup
• Without adapting for MPP
• Use ML scenarios
evolution of Polybase
Partition elimination
Predicate pushdown
Landscape diagram
Local data
External tables
License-free Failover Groups
Powered by
Cost structure
Powered by
Conclusion
• Failover rights benefit removes the license cost from Standby replica
• Failover rights is the benefit on a Failover group level, not instance level, but always applied on the
Secondary
• We support both AHB and PAYG customers
• Benefit for AHB users is getting the licenses back
• Benefit for PAYG users is getting a direct discount
• We support mismatched configurations between the Primary and the Secondary
• The benefit is fully given for all vCores the Secondary holds
• You cannot benefit from Failover rights and AHB at the same time
• To be careful with Failover scenarios when a Secondary instance (covered with Failover rights)
becomes the Primary, as it will lose the benefit and potentially stay unprotected
Demo
License-free Geo-DR
Powered by
Head
Subhead