1. Modernize your database environment with SQL Database Managed Instance
Pieter Vanhove
Modernize your database environment with SQL Database Managed Instance

2. TechNet msftpietervanhove
@Pieter_Vanhove
TechNet msftpietervanhove
PFE

3. What is Managed Instance?
Agenda
What is Managed Instance?
Network Security
New Business Model

4. Azure SQL Database resource types
Single
Elastic Pool
Managed Instance
Database-scoped deployment option with predictable workload performance
Shared resource model optimized for greater efficiency of multi-tenant applications
Instance-scoped deployment option with high compatibility with SQL Server and full PaaS benefits
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

5. The DREAM of the DBA!
Questions

6. Programmability Features
Lift and shift!
Scenario
Enablers
Security
Data Migration
Programmability Features
Operational
Data Migration
Backup/restore
Unique for MI. Take backup from you on-premises DB an simply restore it on the MI. Still the most common migration method
Configurable DB File layout
Seperate tables into different file groups.
Seperate cold data from hot data
DMS
Used to move hunderds of databases in one time and in the near future also to minimize the downtime of migration so that we keep business continutity
Programmability Features
Global temp tables
Cross-database queries and transactions
Linked Server
CLR modules
All these features are alread available in MI.
So if the customer application uses one of these features, changing the connection string should be sufficient
Security
Commitment to provide the most secure platfrom.
MI inherites all the security features that the other SQL products have like SQL Server and Azure DB
Integrated Auth (AAD)
Encryption (TDE, AE)
SQL Audit
Row Level Security
Dynamic Data Masking
Operational
Instance level DMVs and Xevents
SQL Agent – maintenance jobs
DM Mail used for alerts
Allows the customer to use these features that they have used for years 
Scenario Enablers
These features are used in specific scenarios
Some applications on prem have really strong dependencies on these features
Customers gave feedback that these features are needed in the cloud so we have enabled them like
Service broker
CDC
Transactional Replication
More to come when we go GA

7. What is missing? Features Obsolete in the cloud Retired Features
AlwaysOn Availability Groups
Windows Authentication
Management Data Warehouse
Retired Features
Database Mirroring
Extended Stored Procedures
Features for post – GA
Filestream & file tables
Cross Instance Distributed Queries
Stretch Database
Polybase
Policy Based Management
AlwaysOn is used to creat HA/DR and read scale out for on Premises and IaaS.
With MI, the customer get automatically HA in the same region. With a couple of clicks, customer can configure geo-replication to another MI in another data center for read scale out and DR.
We got feedback from customers that sometimes it takes weeks to build a good AlwaysOn Config. So big advantage of MI
Windows Authentication
Used for local application. AD with complex forest.
Moving to cloud, we expect customers to adopt to AAD which is fully support by MI
There is synchronization between on prem AD and AAD.
Another example where MI enables migration and also alows modernaization by moving to the clou
MDW better alternatives like SQL Analytics and OMS. Will be available when going to GA.
Deprecated features like Mirroring and Extended Stored procedures. There is already AlwaysOn and customers should use CLR
Filestream, filetables & Cross-instance distributed transactions will be post GA, because these are features that are related to the OS and there is currently no OS 

8. What with additional services
Will not be installed side-by-side with MI
Recommendation: move to PaaS model
Migrate your SSIS pacakges to new SSIS on Azure Data Factory
Migrate your OLAP models to Azure Analysis Services
Or... Run on Azure Virtual Machines
SSRS – switch to Power BI

9. What is Managed Instance?
Agenda
What is Managed Instance?
Network Security
New Business Model

10. VPN/Express route gateway
Network Security
VNet-to-VNet
Web app (public IP)
VNet2
Network isolation (customer VNET)
SQL instance #1
SQL instance #2
Tenant isolation (compute, storage)
SQL instance #3
VNet1
SQL Database Managed Instance provides complete workload isolation of your workloads through native VNET support. We use virtual data clusters to describe the degree of isolation that customer workloads will experience with SQL Database Managed Instance. During service provisioning (on Azure Portal or through REST API), you can choose the virtual network (VNET) and the subnet to achieve full networking isolation for your Managed Instances. Once created, instances in the VNET can be reached using Azure networking mechanisms (VPN and Express Route gateways).
To two levels of isolation are provided:
Cluster (tenant ring) level: Managed Instances for a tenant are fully isolated from other tenants. No connectivity or resource sharing is possible between different tenants.
Networking level: joining instances to a subnet in a VNET and restricting access to private IP addresses only provides full isolation from public Internet.
“Virtual data cluster” dedicated to customer (virtual private cluster, VNET, private IPs)
VPN/Express route gateway
On-premises

11. Demo

12. What is Managed Instance?
Agenda
What is Managed Instance?
Network Security
New Business Model

13. 2 Managed Instance Options
GENERAL PURPOSE
BUSINESS CRITICAL (Preview)
Best for
Data applications with basic IO and basic availability requirements
Business critical data applications with fast IO and high availability requirements
Compute tiers
Gen4: 8, 16, 24
Gen5: 8, 16, 24, 32, 40, 64, 80
Gen4: 8, 16, 24, 32
Memory
Gen4: 56GB-156GB
Gen5: 44GB-440GB
*Proportional to the number of vCores
Storage
8 TB per instance
Gen 4: 1 TB
Gen 5:
- 1 TB for 8, 16 vCores
- 2 TB for 24 vCores
- 4 TB for 32, 40, 64, 80 vCores
Service tier characteristics
Managed Instance has two service tiers - General Purpose and Business Critical (Public Preview). These tiers provide different capabilities, as described in the table below:
Feature General Purpose Business Critical (preview) Number of vCores* Gen4: 8, 16, 24 Gen5: 8, 16, 24, 32, 40, 64, 80 Gen4: 8, 16, 24, 32 Gen5: 8, 16, 24, 32, 40, 64, 80 Memory Gen4: 56GB-156GB Gen5: 44GB-440GB *Proportional to the number of vCores Gen4: 56GB-156GB Gen5: 44GB-440GB *Proportional to the number of vCores Max storage size 8 TB Gen 4: 1 TB Gen 5: - 1 TB for 8, 16 vCores - 2 TB for 24 vCores - 4 TB for 32, 40, 64, 80 vCores Max storage per database Determined by the max storage size per instance Determined by the max storage size per instance Max number of databases per instance Max database files per instance Up to 280 Unlimited Expected max storage IOPS (depends on data file size). Depends on the underlying SSD speed. .

14. With Azure Hybrid Benefit
Base rate
Total monthly cost of 8 vCore Managed Instance Business Critical option
Up to 30% savings1
Use your on-premises SQL Server licenses to save 30% on Managed Instance.
On-premises license with SA
Deploy and select AHB
Customer total cost
Software
Assurance cost
License included
With Azure Hybrid Benefit
General Purpose (GA)
Business Critical (Preview)*
Pricing (monthly)
License Included
AHB for SQL Server
8 vCores
€1,317
€824
€1,752
€829
16 vCores
€2,633
€1,649
€3,505
€1,659
24 vCores
€3,950
€2,473
€5,258
€2,488
The Azure Hybrid Benefit for SQL Server helps you maximize the value from your current licensing investments and accelerate your migration to the cloud. Azure Hybrid Use Benefit for SQL Server is an Azure-based benefit that enables you to use your SQL Server licenses with Software Assurance to pay a reduced rate (“base rate”) on SQL Database Managed Instance. Azure Hybrid Benefit for SQL Server will be available at public preview (Q1 CY 2018).
DTU model was difficult to understand by the customers.
What is charged
Compute (vCore)
Storage (reserved space)
Backup space (in GA, for the amount that exceeds reserved space)
IOPS (in GA, consumption, per million of operations)
Type of Storage/IO
Included with Compute (per SKU)
Additional price
General Purpose
32 GB
€0.1155/GB
Business critical
€0.1257/GB
IO rate NA
€ per 1 million requests
*Managed Instance Business Critical is in public preview. Prices reflect preview rates

15. Highly virtualized, Enterprise Edition
Core to vCores
SQL Server license trade-in values
SQL Database Managed Instance
Business Critical
General Purpose
Enterprise Edition
Standard Edition OR
Highly virtualized, Enterprise Edition
Virtualization creates a simulated, or virtual, computing environment as opposed to a physical environment. Virtualization often includes computer-generated versions of hardware, operating systems, storage devices, and more. This allows organizations to partition a single physical computer or server into several virtual machines. Each virtual machine can then interact independently and run different operating systems or applications while sharing the resources of a single host machine.
SQL Server Enterprise Edition customers can use an unlimited virtualization benefit for their on-premises workloads. However, moving to the cloud to take advantage of its management, flexibility and cost benefits can be cost prohibitive for some heavily virtualized customers. Managed Instance provides SQL Enterprise Edition customers with Software Assurance the ability to get 4 cores in the cloud for every 1 core they own on-premises for workloads moving to the General Purpose SKU – the SKU that best meets the requirements for highly virtualized workloads. This makes moving virtualized applications to Managed Instance highly cost effective as customers will not have to purchase incremental vCores to move their virtualized application to the cloud.
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 core
1 Enterprise license core = 1 Business Critical core
1 Enterprise license core = 4 General Purpose cores (virtualization benefit)
SQL Server with Software Assurance

16. SQL Offerings in Azure Instance On-premises Lif & shift Migration?
Managed
Instance
SQL
YES
YES NO
On-premises
Lif & shift
Migration?
SQL VMS (IaaS)
Prefer full control
Over
The lowest TCO? NO
Single/ Elastic Pool
SQL

17. SQL Server feature support in Azure SQL Database
SQL Feature
Azure SQL Database
Managed Instance
Always On AG
High availability is included with every database. DR  Failover Groups
High availability is included with every database.
Attach a database No
BACPAC file
Yes
BACKUP Command
Yes with COPY ONLY
CLR
Cross database queries
No – Elastic Queries
Database Mail
Files and file groups
Primary file group only

18. SQL Server feature support in Azure SQL Database
SQL Feature
Azure SQL Database
Managed Instance
Linked Server
No – Elastic Query
Only to SQL Server and SQL Database
Point-in-time restore
Yes
RESTORE statement No
SQL Server Profiler
No – use Extended Events
Yes – but use Extended Events 
Replication
Transactional and snapshot replication subscriber only
Yes - Replication with SQL Database Managed Instance - public preview
Trace Flags
TDE
Partial, only with service-managed encryption

19. What is Managed Instance?
Agenda
What is Managed Instance?
Network Security
New Business Model

20. Before you have questions...

21. How many databases can you create?
Customers can create up to 100 databases within each Managed Instance.

22. Can I specify port number for SQL endpoint?
This option will not be available at Public Preview. Instances will use default port number (1433).

23. Is Transparent Data Encryption supported?
Yes, Transparent Data Encryption will be supported by SQL Database Managed Instance during Public Preview, providing the same service-managed TDE and “on by default” protection for new databases.
During public preview, customers will be able to rely on automatic key management, like in SQL Database today. Over time, we plan to add the ability to leverage Azure Key Vault.

24. Is on-demand backup supported?
Yes, customers can create a copy-only backup in their Azure Blob Storage, however it will only be restorable in Managed Instance.

25. Can a Managed Instance be joined to an Always-On availability group?
Configuring Always-On between Managed Instances is not supported. Every instance is inherently highly available as that is one of the core PaaS capabilities in SQL Database, so there is no need to use Always-On to achieve HA within the Azure region.
If you want a disaster recovery solution that protects you from the Azure region outage, you can use active geo-replication for Managed Instance to replicate databases to another region.
Joining Managed Instance to Always-On availability groups with on-premise SQL Server instances will not be supported initially.

26. Do you still have questions…?

27. Remember… Managed Instance is the dream of the DBA!
Questions

28. BIG Thanks to SQLSatMadrid sponsors
Platinum
Gold

29. Sponsor sessions at 10:15 & 13:00
Don’t miss them, they might be getting distributing some awesome prizes! Also XBOX One & Raffle prizes at 17:45