Resource Monitors are uncomfortable on purpose. That’s why they save money.
Every cloud DWH gives you a way to hard-cap credit spend. Resource Monitors in one, custom quotas in another, usage limits in a third. Same job: stop the query when the budget hits the line.
Almost nobody turns them on.
Ask why and the complaint is always the same: the warehouse suspends mid-deploy, queries die, and someone now has to choose between lifting the cap or waiting until next month’s credit reset.
Yes. That’s the design.
The cap exists to interrupt. The alternative is a runaway dev loop chewing through credits over a weekend nobody is watching. I’ve seen that happen at three clients in the last year.
Teams reach for alerts instead. Dashboards. A Slack channel that pings when usage crosses a threshold. None of those stop the spend. They notify someone after the meter has already moved.
A cap stops it. That’s the whole point.
A budget materializes how much a company is willing to spend. Like any constraint, it forces design choices: which workloads earn a warehouse, which queries run on schedule, which dashboards anyone still opens.
The discipline is three steps: set the cap, let it fire, tune it quarterly. Teams that run that loop stop getting surprised by the bill. The bite is what’s doing the work.
If finance keeps getting surprised by the bill, ask who has the authority to let a query fail.
How many of your warehouses have a hard credit cap set today?