0% found this document useful (0 votes)
589 views

Azure SQL Database

This document provides an overview of Azure SQL Database. Key points include: - Azure SQL Database provides a pool of database resources with high availability and self-healing capabilities. It has fewer controls and limitations than traditional SQL Server. - Azure SQL Database has different pricing tiers for different workload needs, including Basic, Standard, and Premium. - Features like elastic pools, data sync, migration tools, and security options help manage databases in Azure SQL.

Uploaded by

Alex Ivanov
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
589 views

Azure SQL Database

This document provides an overview of Azure SQL Database. Key points include: - Azure SQL Database provides a pool of database resources with high availability and self-healing capabilities. It has fewer controls and limitations than traditional SQL Server. - Azure SQL Database has different pricing tiers for different workload needs, including Basic, Standard, and Premium. - Features like elastic pools, data sync, migration tools, and security options help manage databases in Azure SQL.

Uploaded by

Alex Ivanov
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 9

AZURE SQL DATABASE

..as seen on live tv-show 


AZURE SQL BASIC INFO

 Really nothing more than a pool of database resources


 Is based on the same concept as normal SQL servers
 Highly available
 Self Healing
 99.9 SLA service
AZURE SQL VS. IAAS SQL
Azure SQL IaaS SQL
• There is no infra to access • Manage your own infra
• You have no control over
• Full control over the OS
the OS
• Databases limited to 1TB • Database limited to 64TB

• Limited support for • Bi-directional transaction


transactional replication
replication
• Doesn’t cost as much as a
VM with an SQL license • Support for Hybrid environments

• Fast deployment to use in


just a few minutes
AZURE SQL TIERS

Basic Tier Standard Tier Premium Tier

• Generally used for light • Limitations: 250GB • Destined for heavy


traffic databases workloads
• Needed for Dev and • Also needed for business
testing teams continuity and mission-
critical
• Limitations: 2GB/db, 20
• Limitations: >500GB P1-
workers, 30 logins, 300 P3+P6 and 1TB for P11-P15
concurrent sessions
AZURE SQL ELASTIC POOLS

• Introduced as a necessity to Azure SQL DTUs (Data Transaction Unit) in high and unpredictable
database demand
• It creates a shared database pool, also known as eDTUs
• Limitations: same basic tier, but not the same level (S0-S3, P1, P2, P4, P3/P6, P11, P15)
• 100 eDTUs = 150 DTUs (multiply by 1.5)
AZURE SQL REPLICATION

 Databases heal themselves


 Database restoration: 5 minutes snapshots, hourly, weekly
 Retentions: Basic: 7 Days, Standard: 35 Days
 Geo-restoration: takes 12 hrs, you will loose the last hour of
transcations
 Active Geo-Replication:
• 4 copies of the same database in different regions.
• Sync is seconds away, although 5min are advertised
• Sec DBs are readable, not RW
AZURE SQL DATA SYNC
 Allows to sync 2 or more on-premises SQL
servers
 Sync on-rep and IaaS (on-prem there is an
agent present)
 Hub = main database
 SyncDB – the database that acts as an
witness
 Member DBs are synced to the hub via
the SyncDB
 Hub always wins! (the lottery )
 Work with elastic pools
 Limitations:
• 1db cannot be in more than 5 sync groups
• Sync group cannot have more than 30 dbs
• 500 tables/sync group, 1000
columns/table, 24MB/data row
AZURE SQL MIGRATION

 .BACPAC – encapsulation
 Data Migration Assistant: .BACPAC (Schemas, Data, Users, Server
roles, Logins), Win 7+, .NET 4.5, SQL offline
 Import: command-line (SQLPackage) – included in Mgmt Studio
and SQL Server Data tools; Powershell, Portal
 SQL Server Migration Assistant: Access, DB2, MySQL, Oracle, SAP
ASE
AZURE SQL SECURITY

 Firewall
 Transparent Data Encyption
 Dynamic Data Masking
 SQL Database Auditing And TD
 Best Practices

You might also like