Martin Cairney Hybrid data platform – making the most of Azure plus your on- prem kit DAT341 B.
-
Upload
kenneth-green -
Category
Documents
-
view
214 -
download
0
Transcript of Martin Cairney Hybrid data platform – making the most of Azure plus your on- prem kit DAT341 B.
Spark the future.
Martin Cairney
Hybrid data platform – making the most of Azure plus your on-prem kit
DAT341B
Martin CairneyMicrosoft Data Platform MVP Microsoft Certified Trainer
Organiser – SQL Saturday Melbourne (http://bit.ly/1Mz9Lye)
@martin_cairney
http://au.linkedin.com/in/martincairney
Agenda
Hybrid Solutions with SQL Server 2016Cloud-based AlwaysOn Availability Group Replicas
Stretch Databases
Enhanced Backups to the Cloud
Better consistency in working with SQL Server on-premises, SQL Server on Azure Virtual Machines, and Azure SQL DB means that these solutions can all appear as transparent to your applications.
Hybrid Solutions – AlwaysOn Avaiulability Groups
Cloud-Based AlwaysOn Availability Group Replica
Common On-Premise HA/DR Scenarios:
Less Redundan
cy
• Highly redundant storage on SAN
• Clustering
• vMotion / Live Migration to move VM to another host
More Redundan
cy
• AlwaysOn Availability Groups
Cloud-Based AlwaysOn Availability Group Replica
Primary Site
Remote Site
Primary Replica
Secondary Replica
Secondary Replica
Listener
SQL Server 2012 and later
Multi-Site ClusterMultiple Secondaries but only 1 synchronousListener routes the connections
Primary Site
Primary Replica
Secondary Replica
Secondary Replica
Listener
SQL Server 2016
Extend to Azure Multiple Secondaries: up to 3 synchronousLoad-balanced asynchronous secondariesBasic (2 nodes) for Std EditionListener routes the connections
Azure
Cloud-Based AlwaysOn AvailabilityGroup Replica
As easy as …
1. Ensure your primary is running on a cluster2. Run the wizard3. Enjoy your secondary in Azure
Full HA/DR in Azure Simplified
On Premise Azure
Primary Secondary Forwarder Secondary
Distributed AG
Hybrid Solutions – Stretch Database
Issues with large DB or tablesTables are becoming massive because:
Users want to keep their data forever
Cold data in the tables – accessed infrequently but must be online
Maintenance challenges – backups / DBCC
Stretch DatabasesAllows the movement of entire tables or identified rows and/or columns to be moved to Azure SQL DB
CTP3 limited to moving entire tablesPost-CTP3 release will allow selection of rows/columns based on a predicate
Limitations (as at CTP 3)
Unique / Primary Key constraints not enforcedUPDATE / DELETE operations not permittedALTER TABLE not permitted (other than to set MIGRATION_STATE)Indexed Views cannot reference a stretch table
Stretch DatabasesEligibility Restrictions:
Data types: timestamp sql_variant XML geometry / geography hierarchyid UDTs
Column types: computed columns COLUMN_SET
Constraints: FK constraints that reference the table DEFAULT constraints CHECK constraints
Indexes: XML indexes Full Text indexes Spatial indexes
Table properties: Max 1023 columns Less than 998 indexes FILESTREAM data File Tables Replication CDC or Change Tracking Memory-Optimised
Stretch Databases
Stretching a Table to Azure
Martin Cairney
Hybrid Solutions – Backups in Azure
Enhanced Backups to AzureAzure backup options:
SQL Server 2012
• Backup to Azure blob storage
• Backup to Windows Azure Tool
SQL Server 2014
• URL selectable in SSMS dialog box
• Managed Backup to Windows Azure
SQL Server 2016
• Block blobs can be used to stripe backups
• Snapshots for data files on Azure blob storage
• Enhanced Managed Backup to Windows Azure
Enhanced Backups to AzureBackup to block blobs
Previous versions could only specify a single page blob (max size 1 TB)
Block size is variable up to 4 MB and each block blob can contain up to 50,000 blocks (max block blob size = 195 GB)
Can stripe the backup over multiple files – improving throughput and size of the backup (effectively unlimited)
Requires a Shared Access Signature for the Azure Storage Account (used to create a SQL Credential)
Enhanced Backups to AzureFile-Snapshot Backups
Requires the database files to be hosted on Azure Storage
The .bak file doesn’t contain the data – pointers to the corresponding snapshots
Backup must be to same storage account as the database files use
Enhanced Backups to Azure
File-Snapshot Backups - Mechanism
From MSDN
Azure based backups
Martin Cairney
Complete your session evaluation on My Ignite for your chance to win one of many daily prizes.
Continue your Ignite learning pathVisit Microsoft Virtual Academy for free online training visit https://www.microsoftvirtualacademy.com
Visit Channel 9 to access a wide range of Microsoft training and event recordings https://channel9.msdn.com/
Head to the TechNet Eval Centre to download trials of the latest
Microsoft products http://Microsoft.com/en-us/evalcenter/
© 2015 Microsoft Corporation. All rights reserved.Microsoft, Windows and other product names are or may be registered trademarks and/or
trademarks in the U.S. and/or other countries.MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY,
AS TO THE INFORMATION IN THIS PRESENTATION.