Azure Synapse Analytics Service

Learning Objectives
• Why Warehousing in Cloud
• Azure Synapse Service – a Game Changer
• Traditional vs Modern DW Architecture
• Modern vs Synapse DW Architecture
• Azure Synapse Studio – Unified Experience
• Demo – Provision, Scale, Pause, Firewall settings
Why Warehousing in Cloud ?
Old Data Warehouse
Modern Data Warehouse
Modern Data Warehouse
Azure SQL Data warehosue
Azure Synapse Analytice
"Synapse is the next generation of Azure SQL Data Warehouse,
blending big data analytics, data warehousing, and data integration
into a single unified service that provides end-to-end analytics with
limitless scale."
Azure Synapse Analytics
Azure Synapse Analytics
Unparalleled price-performance

• Up to 14x faster
• Costs 94% less than other
cloud providers
Modern vs Synapse Architecture
Demo – Provision Azure Synapse Service
• 1. Create SQL Server
• 2. Create Synapse SQL Pool (Azure SQL Data Warehouse)
• 3. Pause/Resume Compute Node
• 4. Create Firewall Rule
• 5. Connect with Microsoft SQL Server Management Studio
Azure Synapse Analytics
Geo Backups in Azure Synapse Dedicated SQL pool
Whats is DataWarehouse Snapshot
• A data warehouse snapshot creates a restore point you can leverage to recover or
copy your data warehouse to a previous state. Since dedicated SQL pool is a
distributed system, a data warehouse snapshot consists of many files that are
located in Azure storage. Snapshots capture incremental changes from the data
stored in your data warehouse.
• A data warehouse restore is a new data warehouse that is created from a restore
point of an existing or deleted data warehouse. Restoring your data warehouse is
an essential part of any business continuity and disaster recovery strategy
because it re-creates your data after accidental corruption or deletion. Data
warehouse is also a powerful mechanism to create copies of your data warehouse
for test or development purposes. Dedicated SQL pool restore rates can vary
depending on the database size and location of the source and target data
warehouse.
Automatic Restore Points
• Snapshots are a built-in feature that creates restore points. You do not have to enable
this capability. However, the dedicated SQL pool should be in an active state for restore
point creation. If it is paused frequently, automatic restore points may not be created so
make sure to create user-defined restore point before pausing the dedicated SQL pool.
Automatic restore points currently cannot be deleted by users as the service uses these
restore points to maintain SLAs for recovery.
• Snapshots of your data warehouse are taken throughout the day creating restore points
that are available for seven days. This retention period cannot be changed. Dedicated
SQL pool supports an eight-hour recovery point objective (RPO). You can restore your
data warehouse in the primary region from any one of the snapshots taken in the past
seven days.
• To see when the last snapshot started, run this query on your online dedicated SQL pool.
• select top 1 * from sys.pdw_loader_backup_runs order by run_id desc ;
User-Defined Restore Points
• This feature enables you to manually trigger snapshots to create restore
points of your data warehouse before and after large modifications. This
capability ensures that restore points are logically consistent, which
provides additional data protection in case of any workload interruptions
or user errors for quick recovery time. User-defined restore points are
available for seven days and are automatically deleted on your behalf.
You cannot change the retention period of user-defined restore
points. 42 user-defined restore points are guaranteed at any point in
time so they must be deleted before creating another restore point. You
can trigger snapshots to create user-defined restore points through 
PowerShell or the Azure portal.
Geo-backups and disaster recovery
• A geo-backup is created once per day to a paired data center. The RPO for
a geo-restore is 24 hours. You can restore the geo-backup to a server in any
other region where dedicated SQL pool is supported. A geo-backup
ensures you can restore data warehouse in case you cannot access the
restore points in your primary region.
• If you do not require geo-backups for your dedicated SQL pool, you can
disable them and save on disaster recovery storage costs. To do so, refer
to 
How to guide: Disable geo-backups for a dedicated SQL pool (formerly SQ
L DW)
. Note that if you disable geo-backups, you will not be able to recover your
dedicated SQL pool to your paired Azure region if your primary Azure data
center is unavailable.
Summary
• Advantages of Cloud Warehousing
• Synapse Analytics - advantages
• Why Synapse Analytics is Game changer in Cloud Analytics
• Traditional vs Modern DW Architecture
• Modern vs Synapse DW Architecture
• Synapse Studio – Unified experience
• Demo – Provision, Pause, Scale, Firewall settings etc
• Geo Back ups
Thanks