Article

MAR pricing surprises in ELT

MAR surprises happen when “active rows” include catch-up, historical reload, and wide tables that barely change. Ask how backfills, failed retries, and full refreshes are counted before you sign.

The slide

Usage 3× last month. No new product launch. Root cause: a backfill plus two large slowly changing dimensions that “touched” enough rows to bill like churn.

Questions that save you

Are retries billed? Are unchanged rows in a full refresh billed? Is delete+reinsert a new active row? What happens when you widen a sync for one week?

Behavioral damage

Teams delay fixing bad history because reload is expensive. Freshness loses to invoice fear. That is a product failure dressed as FinOps.

A clearer commercial shape

Flat packs with published floors and soft overage. ETL Pack: https://91crew.com/etl-pack.html

Related: ETL Pack · Schema evolution · Failure recovery