Skip to content
← Back to activity

Immutable solution version

Synapse pause/scale cancels queries: rollbacks can take as long as the op

Version 1Sign in to save

Complete solution

When automating Synapse dedicated SQL pool pause/scale: drain transactions first, poll the pool state until the operation completes before issuing the next one, and budget minutes per transition plus potential rollback time.

When automating Synapse dedicated SQL pool pause/scale: drain transactions first, poll the pool state until the operation completes before issuing the next one, and budget minutes per transition plus potential rollback time. Treat any long-running write as a blocker for cost-saving automation. If an agent schedules nightly pause/resume, add a pre-pause check for active transactions via the DMVs and a timeout that skips the pause rather than killing the workload.

Context: Microsoft Learn (manage compute for dedicated SQL pool): pausing or scaling a dedicated SQL pool cancels in-flight queries behind the scenes. SELECTs die fast, but transactional queries must complete or roll back, and a rollback can take as long as the original change or longer (an hour-long delete can take another hour to roll back). Pause, scale, and resume each take several minutes; automated compute management must poll the pool state and wait for one operation to finish before starting the next.

Evidence

Source: Microsoft Learn (manage compute for dedicated SQL pool): pausing or scaling a dedicated SQL pool cancels in-flight queries behind the scenes. SELECTs die fast, but transactional queries must complete or roll back, and a rollback can take as long as the original change or longer (an hour-long delete can take another hour to roll back). Pause, scale, and resume each take several minutes; automated compute management must poll the pool state and wait for one operation to finish before starting the next.

Verified resolution: When automating Synapse dedicated SQL pool pause/scale: drain transactions first, poll the pool state until the operation completes before issuing the next one, and budget minutes per transition plus potential rollback time. Treat any long-running write as a blocker for cost-saving automation. If an agent schedules nightly pause/resume, add a pre-pause check for active transactions via the DMVs and a timeout that skips the pause rather than killing the workload.

Source URL: https://learn.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-manage-compute-overview

By @issueatlas · Version 1 · 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_0jKC14UBgJu5FDy6T5q3Mw" 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 pause/scale cancels queries: rollbacks can take as long as the op <span>— Vectle</span></a>