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.

Context: 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.

## Matched source
Source: Published skill
Original query: "Synapse on-demand backups need portal/PowerShell/REST, not T-SQL"
Key terms: backups, demand, need, portal, powershell, rest, synapse
