Martin Cairney Hybrid data platform – making the most of Azure plus your on- prem kit DAT341 B

Martin Cairney Microsoft Data Platform MVP Microsoft Certified Trainer Organiser – SQL Saturday Melbourne

Hybrid Solutions with SQL Server 2016 Cloud-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.

Cloud-Based AlwaysOn Availability Group Replica Common On-Premise HA/DR Scenarios: Less Redundancy Highly redundant storage on SAN Clustering vMotion / Live Migration to move VM to another host More Redundancy AlwaysOn Availability Groups

Cloud-Based AlwaysOn Availability Group Replica SQL Server 2012 and later Multi-Site Cluster Multiple Secondaries but only 1 synchronous Listener routes the connections SQL Server 2016 Extend to Azure Multiple Secondaries: up to 3 synchronous Load-balanced asynchronous secondaries Basic (2 nodes) for Std Edition Listener routes the connections Azure

Cloud-Based AlwaysOn Availability Group Replica As easy as … 1.Ensure your primary is running on a cluster 2.Run the wizard 3.Enjoy your secondary in Azure

Full HA/DR in Azure Simplified On Premise Azure Distributed AG

Issues with large DB or tables Tables 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 Databases Allows the movement of entire tables or identified rows and/or columns to be moved to Azure SQL DB CTP3 limited to moving entire tables Post-CTP3 release will allow selection of rows/columns based on a predicate Limitations (as at CTP 3) Unique / Primary Key constraints not enforced UPDATE / DELETE operations not permitted ALTER TABLE not permitted (other than to set MIGRATION_STATE) Indexed Views cannot reference a stretch table

Stretch Databases Eligibility 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

Enhanced Backups to Azure Azure 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 Azure Backup 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 Azure File-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

Continue your Ignite learning path Visit Microsoft Virtual Academy for free online training visit Visit Channel 9 to access a wide range of Microsoft training and event recordings Head to the TechNet Eval Centre to download trials of the latest Microsoft products