Solution skill
Synapse on-demand backups need portal/PowerShell/REST, not T-SQL
Complete solution
Shows how to fix synapse on-demand backups need portal/PowerShell/REST, not T-SQL. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
When building Synapse backup automation, use New-AzSynapseSqlPoolRestorePoint (workspace pools) or the REST API, never T-SQL; it silently cant do this. For long-term retention, restore to a new pool and pause it: storage-only billing while it sits.
Steps
- When building Synapse backup automation, use New-AzSynapseSqlPoolRestorePoint (workspace pools) or the REST API, never T-SQL; it silently cant do this. Cap your logic at 42 user-defined points and prune before creating new ones, and rely on the 8-hour automatic points plus 7-day retention for the safety net. For long-term retention, restore to a new pool and pause it: storage-only billing while it sits.
When to use
You are seeing this: Cap your logic at 42 user-defined points and prune before creating new ones, and rely on the 8-hour automatic points plus 7-day retention for the safety net. Use this skill when you run into "Synapse on-demand backups need portal/PowerShell/REST, not T-SQL".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Microsoft Learn (Synapse backup and restore): T-SQL cannot create an on-demand backup. User-defined restore points are created only through the Azure portal, PowerShell, or REST APIs. 42 user-defined restore points are guaranteed at any point (delete old ones before creating more), and they are auto-deleted after seven days. Automatic restore points are taken every 8 hours. A resumed copy of a restored pool takes only a few minutes to come online.
Verified resolution: When building Synapse backup automation, use New-AzSynapseSqlPoolRestorePoint (workspace pools) or the REST API, never T-SQL; it silently cant do this. Cap your logic at 42 user-defined points and prune before creating new ones, and rely on the 8-hour automatic points plus 7-day retention for the safety net. For long-term retention, restore to a new pool and pause it: storage-only billing while it sits.
Source URL: https://learn.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/backup-and-restore
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_hvgeB1iMqiV-Cqs0XZrqug" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Synapse on-demand backups need portal/PowerShell/REST, not T-SQL <span>— Vectle</span></a>