Azure Synapse serverless vs dedicated SQL pool cost

Quick answer

Synapse serverless SQL pool bills about $5 per terabyte of data scanned by your queries, with no cost when idle, so it is cheapest for intermittent, exploratory querying over well-partitioned data. Dedicated SQL pools bill for provisioned capacity in data warehouse units, for example DW100c at roughly $1.20 per hour (about $876 per month if run continuously), regardless of query volume, so they suit steady, high-concurrency analytical workloads. The rule: serverless for occasional queries and ad hoc exploration, dedicated for constant heavy analytics, and pause dedicated pools when idle since they bill while provisioned even without queries.

Azure Synapse Analytics gives you two ways to run SQL analytics, and they sit at opposite ends of the cost model. Serverless SQL pools charge only for the data your queries scan, so you pay per use. Dedicated SQL pools reserve a fixed amount of compute and charge for it by the hour whether or not you query. Choosing between them is about query frequency and volume.

The two cost models

Pool	Billing basis	Idle cost
Serverless SQL	~$5 per TB scanned	None
Dedicated SQL (DWU)	Per hour of provisioned capacity	Full rate while running

Serverless bills roughly $5 per terabyte scanned, so a query touching 100 GB costs about $0.50 and an idle pool costs nothing. Dedicated bills by data warehouse unit: a DW100c runs about $1.20 per hour, roughly $876 per month if left running continuously, and higher DWU levels scale up from there, regardless of how many queries you run.

Where serverless wins

Serverless is cheapest for intermittent, exploratory, and ad hoc querying, analysts running a few queries a day, occasional reporting, or querying data in a data lake without loading it into a warehouse. Because you pay only for data scanned and nothing when idle, sporadic use costs little. The key to keeping it cheap is scanning less: partitioning, columnar formats like Parquet, and predicate pushdown reduce the terabytes each query touches, the same discipline as the BigQuery on-demand optimization.

Where dedicated wins

Dedicated SQL pools win for steady, high-concurrency analytical workloads: a busy data warehouse serving many users and dashboards throughout the day, running large joins and aggregations constantly. At that intensity, per-terabyte serverless scanning would add up fast, while the fixed hourly dedicated cost delivers consistent performance and predictable spend. Dedicated also supports features and performance tuning that heavy warehousing needs, as the broader Synapse cost guide covers.

Pause dedicated pools when idle

The biggest dedicated-pool waste is leaving it provisioned when nobody is querying. Because it bills by the hour while running, a DW warehouse left on overnight and on weekends pays for idle capacity. Pausing the pool when not in use, and resuming it for the working day, can cut its cost substantially, since a pool run only during business hours costs a fraction of one run continuously. Automating pause and resume around the usage schedule is a high-value, low-effort saving.

Choosing the pool on cost

Estimate query frequency and the data volume each query scans. For occasional queries over well-partitioned data, serverless is far cheaper. For constant heavy analytics, dedicated with disciplined pausing is cheaper and more predictable. Many teams use both: serverless for ad hoc exploration of the lake, dedicated for the core warehouse. Price both against the resource catalog before you deploy so the crossover between per-scan and provisioned pricing is clear for your workload.

FAQ

How does Synapse serverless SQL pool bill?

It bills about $5 per terabyte of data scanned by your queries, with no charge when idle. A query touching 100 GB costs roughly $0.50. Because you pay only for data scanned, sporadic and exploratory querying is cheap, and the way to keep it cheap is to scan less through partitioning, columnar formats like Parquet, and predicate pushdown that reduce the data each query touches.

How does a Synapse dedicated SQL pool bill?

It bills for provisioned capacity in data warehouse units by the hour, regardless of query volume. A DW100c runs about $1.20 per hour, roughly $876 per month if left running continuously, with higher DWU levels costing more. Because it bills while provisioned even without queries, leaving a dedicated pool running when idle wastes money, so pausing it when unused is important.

When is Synapse serverless cheaper than dedicated?

For intermittent, exploratory, and ad hoc querying, such as analysts running a few queries a day, occasional reporting, or querying a data lake directly. Paying only for data scanned and nothing when idle makes sporadic use very cheap. For constant high-concurrency warehousing, per-terabyte scanning adds up and dedicated's fixed hourly cost becomes cheaper and more predictable.

Should I pause a dedicated SQL pool?

Yes, whenever it is not in use. Because a dedicated pool bills by the hour while running, leaving it on overnight and on weekends pays for idle capacity. Pausing when not in use and resuming for the working day can cut its cost substantially, since a pool run only during business hours costs a fraction of one run continuously. Automate the pause and resume around usage.

How does C3X help with Synapse cost?

C3X prices Synapse configurations from Terraform before you deploy, including serverless and dedicated SQL pools, so the per-scan and provisioned cost models are visible in the pull request. That lets you compare the two against your expected query frequency and volume at design time and choose serverless for ad hoc work or a properly paused dedicated pool for steady warehousing.

What to do next

Compare Synapse serverless and dedicated before you deploy. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.