Snowflake warehouse auto-suspend vs always-on dev cost

Careful with NULL in join keys, they'll drop rows in an inner join.

Document the grain decision, most BI bugs turn out to be grain bugs.

How do you handle backfill without duplicating rows?

Tried that, partial improvement but lag still spikes on redeploy.

In our case the root cause was an implicit cast preventing pushdown.

Plain English: the system prefers to guess a good-enough plan than the perfect plan, because figuring out the perfect plan would take longer than just running the good-enough one.