Should I move my databaseto the cloud?

James SerraBig Data Evangelist

Microsoft

JamesSerra3@gmail.com

(On-prem vs IaaS VM vs SQL DB/DW)

About Me

▪ Microsoft, Big Data Evangelist

▪ In IT for 30 years, worked on many BI and DW projects

▪ Worked as desktop/web/database developer, DBA, BI and DW architect and developer, MDM

architect, PDW/APS developer

▪ Been perm employee, contractor, consultant, business owner

▪ Presenter at PASS Business Analytics Conference, PASS Summit, Enterprise Data World conference

▪ Certifications: MCSE: Data Platform, Business Intelligence; MS: Architecting Microsoft Azure

Solutions, Design and Implement Big Data Analytics Solutions, Design and Implement Cloud Data

Platform Solutions

▪ Blog at JamesSerra.com

▪ Former SQL Server MVP

▪ Author of book “Reporting with Microsoft SQL Server 2012”

Should I move my database to the cloud?

Let me show you why…

Agenda

▪ SQL Server on-prem

▪ SQL Server continuum

▪ SQL Server in an Azure VM (IaaS)

▪ Azure SQL Database (PaaS/DBaaS)

▪ Azure SQL Data Warehouse (PaaS/DBaaS)

Benefits of the cloud

Agility• Unlimited elastic scale

• Pay for what you need

Innovation• Quick “Time to market”

• Fail fast

Risk• Availability

• Reliability

• Security

Total cost of ownership calculator: https://www.tco.microsoft.com/

Reasons not to move a database to cloud

• No internet connection (deep mine, submarine) or slow internet connection (offshore oil rig, cruise ship)

• Millisecond performance required (servers in high-volume package plant)

• Applications will stay on-prem

• Locked-in lease of datacenter with new equipment

• Large amount of on-prem born data

• Huge migration effort for a short life span database

• Extremely sensitive data

This just means some databases should not be moved, but many others can!

What would it take to build my own DB on-prem?

Why go through all this?

If you have your own data center, you are in the air conditioning business

Managed data lake with

SQL Server and Spark

SQL Server

Data virtualization

T-SQL

Analytics Apps

Open

database

connectivity

NoSQL Relational

databases

HDFS

Complete AI platform

SQL Server External Tables

Compute pools and data pools

Spark

Scalable, shared storage (HDFS)

External

data sources

Admin portal and management services

Integrated AD-based security

SQL Server

ML Services

Spark &

Spark ML

HDFS

REST API containers

for models

Managing all dataIntegrating all data AI over all data

Data Modernization on Premises

It can handle up to 384-cores and 48TB of memory! It supports various storage devices including the HPE 3PAR StoreServ 10000

storage array which supports up to 3.2PB of disk space.

https://www.hpe.com/us/en/product-catalog/servers/integrity-servers/pip.hpe-integrity-superdome-x-server.7161269.html

Data Warehouse Fast Track for SQL ServerA data warehouse-specific database system design and validation program

for Microsoft partners and customers.

Database configuration

• Workload-specific.

• Database architecture.

• SQL Server settings.

• Operating system settings.

• Performance guidance.

Software

• SQL Server Enterprise.

• Windows Server Enterprise.

• Red Hat Enterprise Linux.

• SUSE Linux Enterprise Server

Windows Server

or Linux

SQL Server

Hardware system design

• Partners offer optimally configured

systems certified by Microsoft.

• Resource balanced and validated for

data warehouse workloads.

• Latest-generation servers and storage,

including solid-state disks (SSDs).

Processors

Networking

Servers

Storage

https://www.microsoft.com/en-us/sql-server/data-warehousing

Parallelism

• Uses many separate CPUs running in parallel to execute a single

program

• Shared Nothing: Each CPU has its own memory and disk (scale-out)

• Segments communicate using high-speed network between nodes

MPP - Massively

Parallel

Processing

• Multiple CPUs used to complete individual processes simultaneously

• All CPUs share the same memory, disks, and network controllers (scale-up)

• All SQL Server implementations up until now have been SMP

• Mostly, the solution is housed on a shared SAN

SMP - Symmetric

Multiprocessing

Microsoft Analytics Platform System

www.microsoft.com/aps

Microsoft Big Data Portfolio

SQL Server Stretch

Business intelligence

Machine learning analytics

Insights

SQL Server 2017

SQL Server 2017 Fast Track

Azure SQL DW

Databricks

Cosmos DB

HDInsight

Hadoop

Analytics Platform System

Sequential Scale Out + AcrossScale Up

Key

Relational Non-relational

On

-pre

mis

es

Clo

ud

Microsoft has solutions covering

and connecting all four

quadrants – that’s why SQL

Server is one of the most utilized

databases in the world

Azure SQL Database

SQL Server in Azure VM

Data platform continuumHybrid Cloud

On premises

Shared

Lower cost

Dedicated

Higher cost

Higher administration Lower administration

Off premises

Who manages what?

Infrastructureas a Service

Storage

Servers

Networking

O/S

Middleware

Virtualization

Data

Applications

Runtime

Man

ag

ed

by M

icroso

ft

Yo

u s

cale

, m

ake

resi

lien

t &

man

ag

e

Platformas a Service

Sca

le, R

esilie

nce

an

d

man

ag

em

en

t by M

icroso

ft

Yo

u m

an

ag

e

Storage

Servers

Networking

O/S

Middleware

Virtualization

Applications

Runtime

Data

On PremisesPhysical / Virtual

Yo

u s

cale

, m

ake r

esi

lien

t an

d m

an

ag

e

Storage

Servers

Networking

O/S

Middleware

Virtualization

Data

Applications

Runtime

Softwareas a Service

Storage

Servers

Networking

O/S

Middleware

Virtualization

Applications

Runtime

Data

Sca

le, R

esilie

nce

an

d

man

ag

em

en

t by M

icroso

ft

Windows Azure

Virtual Machines

Windows Azure

Cloud Services

One consistent platform

with common tools.

CloudOn-Premises

The data platform continuum

Need control over / access to the operating system

Have to run the app or agents side-by-side with the DB

Need to use older version of SQL Server

To run SSRS

DW in the 4TB-50TB range

3rd-party app not certified for PaaS

Control over backups and maintenance window

▪ VM hosted on Microsoft Azure Infrastructure (“IaaS”)• From Microsoft images (gallery) or your own images (custom)

SQL 2008R2 / 2012 / 2014 / 2016 / 2017 Web / Standard / Enterprise

Images refreshed with latest version, SP, CU

• Windows Server 2008 R2 / 2012 R2 / 2016, Linux RHEL / Ubuntu

• Fast provisioning (~10 minutes).

• Accessible via RDP and Powershell

• Full compatibility with SQL Server “Box” software; 99.95% SLA

▪ Pay per use• Per minute (only when running)

• Cost depends on size and licensing

• EA customers can use existing SQL licenses (BYOL)

• Network: only outgoing (not incoming)

• Storage: only used (not allocated)

▪ Elasticity• 1 core / 2 GB mem / 1 TB → 128 cores / 3.5 TB mem / 2 PB

▪

▪

▪

▪

▪

▪

▪

▪

▪

▪

▪

▪

▪

▪

Azure calculator: https://azure.microsoft.com/en-us/pricing/calculator/

VM Gallery Images via Azure MarketplaceCertified pre-configured software images (7020 on 4/3/2019)

https://azuremarketplace.microsoft.com/en-us/marketplace/apps or Azure web portal -> Create a resource -> Azure Marketplace (see all)

Azure Quickstart TemplatesFree community contributed templates (766 on 4/3/19) https://azure.microsoft.com/en-us/documentation/templates/

Virtual Machine storage architecture

C:\

OS disk (127 GB)Usually 115 GB free. A .vhd file

E:\, F:\, etc.

or storage spaces

Data disks

Attach SSD/HDD up to 32TB. These

are .vhd files

D:\

Temporary disk(Contents can be lost)

SSD/HDD and size depends on VM

chosenDisk Cache

Azure Blob Storage▪ Azure Storage Page Blobs, 3 copies

▪ Storage high durability built-in (like have RAID)

▪ Managed disks, up to 32 TB per disk (2 PB total)

▪ (Ultra SSD in preview, 64 TB disks, 4 PB total)

▪ SLA: 99.9%

▪ 11 9s of durability

Storage configuration

Automatically creates one

Windows storage space

(virtual drive) across all disks.

Up to 64 32TB disks for 2 PB

of drive space.

Azure Regions

◼ 100+ datacenters

◼ Top 3 networks in the world

◼ 2.5x AWS, 7x Google DC Regions

◼ M Series – Largest VM in World, 128 cores, 3.5TB mem, local 4 TB SSD, 2PB data disks

Migrating Data

Migrate from on-prem SQL server to Azure VM IaaS:

• Use the Deploy a SQL Server Database to a Microsoft Azure VM wizard. Recommended method for migrating an on-premises user database

when the compressed database backup file is less than 1 TB. Use on SQL Server 2005 or greater to SQL Server 2014 or greater

• Perform on-premises backup using compression and manually copy the backup file into the Azure virtual machine and then do a restore (only if

you cannot use the above wizard or the database backup size is larger than 1 TB). Use on SQL Server 2005 or greater to SQL Server 2005 or

greater

• Perform a backup to URL and restore into the Azure virtual machine from the URL. Use on SQL Server 2012 SP1 CU2 or greater to SQL Server

2012 SP1 CU2 or greater

• Detach and then copy the data and log files to Azure blob storage and then attach to SQL Server in Azure VM from URL. Use on SQL Server 2005

or greater to SQL Server 2014 or greater

• Convert on-premises physical machine to Hyper-V VHD, upload to Azure Blob storage, and then deploy as new VM using uploaded VHD. Use

when bringing your own SQL Server license, when migrating a database that you will run on an older version of SQL Server, or when migrating

system and user databases together as part of the migration of database dependent on other user databases and/or system databases. Use on

SQL Server 2005 or greater to SQL Server 2005 or greater

• Ship hard drive using Windows Import/Export Service. Use when manual copy method is too slow, such as with very large databases. Use on SQL

Server 2005 or greater to SQL Server 2005 or greater

• If you have an AlwaysOn deployment on-premises and want to minimize downtime, use the Add Azure Replica Wizard to create a replica in Azure

and then failover, pointing users to the Azure database instance. Use on SQL Server 2012 or greater to SQL Server 2012 or greater

• If you do not have an AlwaysOn deployment on-premises and want to minimize downtime, use SQL Server transactional replication to configure

the Azure SQL Server instance as a subscriber and then disable replication, pointing users to the Azure database instance. Use on SQL Server

2005 or greater to SQL Server 2005 or greater

• Others: data-tier application, transact-SQL scripts, sql server import and export wizard, SSIS, copy database wizard

Azure Database Migration Service (DMS)

A seamless, end-to-end solution for moving on-premises SQL Server, Oracle, and other relational

databases to the cloud.

Azure Database Migration Guide

https://datamigration.microsoft.com/

Scale VMs

Scale VMs

PowerShell script

Automated Management

SQL Server IAAS

• Optimization to a target workload (OLTP / DW)• Best performance practices for SQL Server and Storage

• Automated Patching

• Automated Backup

• SQL Server AlwaysOn High Availability

• Advanced Analytics

Simplify common operations

Now protects System DBs

and allow scheduling

Monitoring

SQL Server IAAS

Monitor SQL Perf Counters in Azure PortalEvaluates ~100 best

practices

Plus:

- System Center

- DMVs, Profiler, XEvents

Operations Insights Portal

HA/DR deployment architectures

Azure Only Availability replicas running across multiple Azure regions in Azure VMs for disaster recovery.

Cross-region solution protects against complete site outage.

Replicas running in same Azure Region for HA.

Hybrid Some availability replicas running in Azure VMs and other replicas running on-premises for cross-site disaster recovery.

HA only, not DR FCI on a two-node WSFC running in Azure VMs with storage supported by storage spaces direct.

Azure OnlyPrincipal and mirror and servers running in different datacenters for disaster recovery.

Principal, Mirror, and Witness run within same Azure data center, deployed using a DC or server certificates for HA.

HybridOne partner running in an Azure VM and the other running on-premises for cross-site disaster recovery using server certificates.

For DR only / Hybrid only

One server running in an Azure VM and the other running on-premises for cross-site disaster recovery.

Log shipping depends on Windows file sharing, so a VPN connection between the Azure virtual network and the on-premises network is required.

Requires AD deployment on DR site.

On-prem or Azure production databases backed up directly to Azure blob storage for disaster recovery.

SQL 2016: Backup to Azure with file snapshots

Simpler BCDR storySite Recovery makes it easy to handle replication, failover and recovery for your on-premises workloads and applications (not data!).

Flexible replication You can replicate on-premises servers, Hyper-V virtual machines, and VMware virtual machines.

Eliminate the need for secondary

Native support for

SQL Server data files

stored as Azure blobs

Performance Best Practices

SQL Server IAAS

VM size DS3 or higher for SQL Enterprise edition.

DS2 or higher for SQL Standard and Web editions.

Storage Use Premium Storage. Standard storage is only recommended for dev/test.

Keep the storage account and SQL Server VM in the same region.

Disable Azure geo-redundant storage (geo-replication) on the storage account.

Disks Use a minimum of 2 P30 disks (1 for log files; 1 for data files and TempDB).

Avoid using operating system or temporary disks for database storage or logging.

Enable read caching on the disk(s) hosting the data files and TempDB.

Do not enable caching on disk(s) hosting the log file.

Stripe multiple Azure data disks to get increased IO throughput.

Format with documented allocation sizes.

I/O Enable database page compression.

Enable instant file initialization for data files.

Limit or disable autogrow on the database.

Move all databases to data disks, including system databases.

Move SQL Server error log and trace file directories to data disks.

default backup and database file locations.

Apply SQL Server performance fixes.

Feature specific Back up directly to blob storage.

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-performance

Scales

on the fly

Learns

& adapts

Works in your

environment

Secures

& protects

Enables

multi-tenant

SaaS apps

A Z U R E S Q L D ATA B A S E T H E I N T E L L I G E N T R E L A T I O N A L C L O U D D A T A B A S E S E R V I C E

Realize automatic performance improvements from continuous assessments

Change service tiers, performance levels, and storage dynamically with minimal downtime

Easily manage and monitor multitenant apps, and benefit from database isolation

Develop your app and connect to SQL Database with the tools and platforms you prefer

Build security-enhanced, highly compliant apps with built-in protection and intelligent Threat Detection.99.99% SLA, Geo-Replication, & Point-in-time-Restore

B U I L D B E T T E R A P P S W I T H

A Z U R E S Q L D ATA B A S E

*Data source & customer quotes: The Business Value of Microsoft Azure SQL Database Services, IDC, March 2015

Faster time to marketIncreased productivity

Reduced risksLower TCO

47% staff time

reclaimed for other tasks

75% faster app

deployment cycles than

competing databases

53% less expensive

than on-premises/hosted

71% fewer cases

of unplanned downtime

than competing databases

Designed for predictable performance

Across Basic, Standard, and Premium, each performance level is

assigned a defined level of throughput

Introducing the Database Transaction Unit (DTU) which

represents database power and replaces hardware specs

Redefined

Measure of

power

% CPU

% read % write

% memory

Basic — 5 DTU S0 — 10 DTU

S1 — 20 DTU

S2 — 50 DTU

S3 — 100 DTU

DTU is defined by the bounding box for the

resources required by a database workload and

measures power across the six performance levels.

P1 — 125 DTU

P2 — 250 DTU

P4 — 500 DTU

P6 — 1,000 DTU

P11 — 1,750 DTU

P15 — 4,000 DTU

DTU-BASED SINGLETON SERVICE TIERS

Basic Standard Premium

S0 S1 S2 S3 S4 S6 S7 S9 S12 P1 P2 P4 P6 P11 P15

Built forLight transactional

workloadsMedium transactional workloads Heavy transactional workloads

Available SLA 99.99%*

Database max size 2 GB 250 GB 1 TB 4 TB

Point-in-time restore

(“oops” recovery)Any point within 7 days Any point within 35 days

Business continuity Active geo-replication, up to four readable secondary backups

Security Auditing, row-level security, dynamic data masking, Advanced Threat Protection

Performance

objectivesTransactions per hour Transactions per minute Transactions per second

Database transaction

units (DTUs)5 10 20 50 100 200 400 800 1,600 3,000 125 250 500 1,000 1,750 4,000

*The 99.99% availability SLA does not apply to the existing Web and Business editions, which will continue to be supported at 99.9% availability.

Scale DTU’s

GEN5 VCORE-BASED SINGLETON SERVICE TIERS

General Purpose Business Critical

2 4 8 16 24 32 48 80 2 4 8 16 24 32 48 80

Built for Most business workloads Business applications with high IO requirements

Available SLA 99.99%*

Memory 11 GB 22 GB 44 GB 88 GB 132 GB 176 GB 264 GB 440 GB 11 GB 22 GB 44 GB 88 GB 132 GB 176 GB 264 GB 440 GB

Backups RA-GRS, 7-35 days (7 days by default) RA-GRS

Availability 1 replica, no read-scale 3 replicas, 1 read-scale, zone redundant HA

Business

continuityActive geo-replication, up to four readable secondary backups

Max data size

(GB)1024 1536 3072 4096 1024 2048 4096

Target IOPS

(64 KB)500 1000 2000 4000 6000 7000 5000 10,000 20,000 40,000 60,000 80,000 100,000 200,000

*The 99.99% availability SLA does not apply to the existing Web and Business editions, which will continue to be supported at 99.9% availability.

Scale vCores

Mission-critical business continuity on your

terms, via programmatic APIs

ACTIVE GEO-REPLICATION

Up to 4 secondaries

(can go higher via secondary of a secondary - a

process known as chaining)

Service levelsBasic, standard, premium

Self service

Readable secondaries Up to 4

Regions available Any Azure region

Replication Automatic, asynchronous

Manageability tools REST API, PowerShell, or Azure

Portal

Recovery time objective

(RTO)<1 hour (differential backup to

another region)

Recovery point objective<5 minutes (transaction log

backup)

Failover On demand

Setup Disaster Recovery

P

S S

Reads are completed at the primary

Writes are replicated to secondaries

Single logical database

Write

Write Ack

Ack

Read

write

Ack

value

Recovery from machine failure

Critical capabilities:

✓ Create new replica

✓ Synchronize data

✓ Stay consistent

✓ Detect failures

✓ Failover

✓ 99.99% availability

HIGH-AVAILABILITY PLATFORM

DB P S

P S

At no extra costs, the Read Scale-Out feature allows you to load balance SQL Database read-only

workloads using the capacity of one of the read-only replicas when using the Premium or Business

Critical tier.

READ SCALE-OUT

Geo- replicated

Restore from backup

Azure SQL

Database backups

Automatic backups

Self-service restore

Tiered retention policy

10 years, Long-term backup retention

POINT-IN-TIME RESTORE

sabcp01bl21

Azure storage

sabcp01bl21

GEO-RESTORE PROTECTS FROM DISASTER

Geo- replicated

Restore to any Azure region

Azure SQL

Database backups

sabcp01bl21

Azure storage

sabcp01bl21

ERT and RPO and RTO

ERT = Estimated Recovery Time: The estimated duration for the database to be fully functional after a restore/failover request

RPO = Recovery Point Objective: The amount of most recent data changes (time interval) the application could lose after recovery

RTO = Recovery Time Objective: Maximum acceptable time before the application fully recovers after the disruptive event (only applicable if the automated failover policy is configured)

Y O U R D ATA B A S E O N A U T O P I L OTBUILT-IN ADMIN AND DATA PROTECTION

Fully managed activities like maintenance, security, updates, DR and back-ups

No application downtime

Save money, time and worryAzure SQL Database

Learns & adapts

Infrastructure maintenance

Security and

software patches

Feature updates

Disaster recovery failover

Automatic back-ups

T H R E AT A N D A N O M A LY D E T E C T I O NADVANCED SECURITY AND COMPLIANCE

Intelligent threat detection

Built-in behavioral analysis

Real-time alerts

Explorable audit log

Unusual patterns are detected and fixed

Discover, track and remediate vulnerabilities

SQL Threat Detection

Azure SQL Database

Web app

External attacker /

malicious insider

End user experiencing

errors & issues

Real-time threat alerts to admins

Real-time alerts to developers

Machine Learning

Anomaly detection

Learns & adapts

S E L F - T U N I N G P E R F O R M A N C EDATABASE ADVISOR AND ADAPTIVE QUERY PROCESSING

Manages indexes, tailored to the specific workload

Tests and validates actions, reverts if impact negative

Runs in full auto-mode, or in recommend/review mode

Continuously monitors query patterns and performance

Tuning

algorithms

SQL Database Database advisor

Developerno admin skills

DBA ofmany databases

“My app gets

auto-tuned” “I can do more

in less time”

Learns & adapts

MIGRATION TOOLS

My blog:

Migrate from on-prem SQL server to Azure

SQL Database

Microsoft database migration tools

Azure Database Migration Guide

https://datamigration.microsoft.com/

Single databases limitations

• VNET

• Cross database joins

• Resource Governor

• SQL Agent

• CLR

• Change Data Capture

See https://docs.microsoft.com/en-us/azure/sql-database/sql-database-features,

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-transact-sql-information

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

S AV E T I M E W I T H FA M I L I A R S Q L S E R V E R T O O L S A N D R E S O U R C E SEliminate app changes with full SQL Server

programming surface

Use familiar SQL Server features in SQL Database

Managed Instance

Native backup and restore

Cross-database queries and transactions

Broad security features including Transparent Data Encryption, SQL Audit, Always Encrypted and Dynamic Data Masking

SQL Agent, DBMail, and Alerts for workload orchestration improved awareness

Scenario enablers including Change Data Capture, Service Broker, Transactional Replication, and CLR

DMVs, XEvents, and Query Store for troubleshooting

Full compatibility with SQL Server 2005+

Instance subnet

SQL Instance #1

storage account

Front end subnet

RESTORE 12 BACKUP TO AZURE

SQL on VMREPOINT APP3

Backup/Restore to Managed Instances

This can be automated with the Azure Database Migration Service

Choice drives our approach to resource

management and pricing

Simplicity

Flexibility

Customers pay for:

COMMITTED TO CUSTOMER CHOICE

General purpose Business critical

Best for Most business workloads. Offers budget-

oriented balanced and scalable compute

and storage options.

Business applications with high IO

requirements. Offers highest resilience to

failures using several isolated Always On

replicas.

Compute tiers Two hardware generations to choose from

Single/Elastic

Pools

Managed

Instance

Single/Elastic

Pools

Managed

Instance

1 to 72 vCores 8, 16, 24 vCores 1 to 72 vCores8, 16, 24, 32, 40, 64,

80 vCores

Storage Premium remote storage (per instance) Super-fast local SSD storage (per

instance)

Single/Elastic

Pools

Managed

Instance

Single/Elastic

Pools

Managed

Instance

5GB – 4TB 32GB – 8TB 5GB – 4TB 32GB – 4TB

Availability 1 replica, no read-scale 3 replicas, 1 read-scale, zone-redundant

HA

Backups RA-GRS, 7-35 days (7 days by default) RA-GRS, 7-35 days (7 days by default)

Azure SQL Data WarehouseA relational data warehouse-as-a-service, fully managed by Microsoft.

Industries first elastic cloud data warehouse with enterprise-grade capabilities.

Support your smallest to your largest data storage needs while handling queries up to 100x faster.

SQL DW: Building on SQL DB Foundation

Elastic, Petabyte Scale

DW Optimized

99.99% uptime SLA,

Geo-restore

Azure Compliance (ISO, HIPAA, EU, etc.)

True SQL Server Experience;

Existing Tools Just Work

SQL DW

SQL DB

Service Tiers

SMP vs MPP

Elastic scale & performance

Real-time elasticity

Resize in <1 minute On-demand compute

Expand or reduce

as needed

Scale DWU’s

Market leading price/performance

Query unstructured data via PolyBase/T-SQL

PolyBase

Scale out compute

SQL DW Instance

Hadoop VMs /

Azure Storage

Any data, any size, anywhere

When Paused, Pay only for StorageUse it only when you need it – no reloading / restoring of data

Save Costs with Dynamic Pause and Resume

• When paused, cloud-scale storage is min cost.

• Policy-based (i.e. Nights/weekends)

• Automate via PowerShell/REST API

• Data remains in place

• Auto backups, every 4 hours

• On-demand backups in Azure Storage

• REST API, PowerShell or Azure Portal

• Scheduled exports

• Near-online backup/restore

• Backups retention policy:

• Auto backups, up to 35 days

• On-demand backups

retained indefinitely

Geo- replicated

Restore from backup

SQL DW backups

sabcp01bl21

Azure Storage

sabcp01bl21

Automatic backup and geo-restoreRecover from data deletion or alteration or disaster

Limitations and Enhancements

Limitations:

• ANSI joins on updates

• ANSI joins on deletes

• merge statement

• cross-database joins

• cursors

• INSERT..EXEC

• output clause

• inline user-defined functions

• multi-statement functions

• common table expressions

• [recursive common table expressions (CTE)](#Recursive-common-table-

expressions-(CTE)

• CLR functions and procedures

• $partition function

• table variables

• table value parameters

• distributed transactions

• commit / rollback work

• save transaction

• execution contexts (EXECUTE AS)

• group by clause with rollup / cube / grouping sets options

• nesting levels beyond 8

• updating through views

• use of select for variable assignment

• no MAX data type for dynamic SQL strings

See https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-migrate-code

Best practices:

https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-best-practices

Load data:

https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-overview-load

Azure Free Account https://azure.microsoft.com/en-us/free/

Azure Free Account

In closing…

Moving to the cloud is a “no brainer”, it’s just a question of when!

Q & A ?James Serra, Big Data Evangelist

Email me at: JamesSerra3@gmail.com

Follow me at: @JamesSerra

Link to me at: www.linkedin.com/in/JamesSerra

Visit my blog at: JamesSerra.com (where this slide deck is posted under the “Presentations” tab)