Performance tuning & optimization for Teradata → Snowflake
Teradata tuning habits (spool management, index/PI assumptions, and optimizer-specific shapes) don’t translate. We tune Snowflake layout, query shapes, and warehouse posture so pruning works, credits stay stable, and refresh SLAs hold under real concurrency.
- Input
- Teradata Performance tuning & optimization logic
- Output
- Snowflake equivalent (validated)
- Common pitfalls
- Carrying over PI/index thinking: expecting physical design to rescue query shape; Snowflake needs pruning-first predicates and evidence-driven clustering.
- Clustering by folklore: clustering keys chosen without evidence from predicates/join keys.
- Full-target MERGE: missing apply boundaries causes large scans and credit spikes.
Why this breaks
Teradata performance tuning is often encoded in physical design and platform behavior: PI/index assumptions, spool management, and optimizer-driven query plans. After migration, teams keep Teradata-era query shapes and expect Snowflake to behave similarly—then costs spike and SLAs slip because Snowflake’s model is different. In Snowflake, credit burn is driven by warehouse usage and scan footprint, and MERGE/apply workloads can become full-target scans without bounded scope.
Common post-cutover symptoms:
- Queries scan too much because predicates don’t prune effectively
- Join-heavy reporting reshuffles large datasets; BI latency increases
- MERGE/apply jobs scan full targets; credit burn becomes unpredictable
- BI refresh contends with batch loads without warehouse isolation
- Improvements regress because there are no baselines or gates
How conversion works
- Baseline top workloads: identify the most expensive and most business-critical queries/pipelines (dashboards, marts, incremental loads).
- Diagnose root causes: pruning effectiveness, join patterns, large scans, and MERGE scope.
- Tune data layout: evidence-driven clustering where beneficial based on access paths (not folklore).
- Rewrite for bounded applies: staged apply, bounded MERGE scopes, and pruning-friendly predicates.
- Warehouse posture: isolate batch vs BI warehouses, tune concurrency and sizing, and implement credit guardrails.
- Regression gates: store baselines and enforce thresholds so improvements persist.
Supported constructs
Representative tuning levers we apply for Teradata → Snowflake workloads.
| Source | Target | Notes |
|---|---|---|
| PI/index-era performance assumptions | Pruning-first predicates + evidence-driven clustering | Replace physical tuning with scan-footprint reduction. |
| Spool-sensitive query shapes | Bounded scans + staged materializations | Reduce large intermediate explosions and stabilize runtime. |
| MERGE/upsert pipelines | Bounded MERGE scopes + staged apply | Avoid full-target scans and unpredictable credit burn. |
| Join-heavy BI workloads | Pruning-aware rewrites + pre-aggregation/materializations | Stabilize dashboards and reduce repeated large scans. |
| Mixed BI + batch contention | Warehouse isolation + concurrency posture | Prevent batch workloads from impacting BI latency. |
| Ad-hoc cost spikes | Governance guardrails + regression gates | Prevent credit blowups from unmanaged changes. |
How workload changes
| Topic | Teradata | Snowflake |
|---|---|---|
| Primary cost driver | Platform capacity + spool behavior | Warehouse credits + scan footprint |
| Data layout impact | PI/indexes and optimizer behavior | Clustering is optional and evidence-driven |
| Incremental apply | MERGE logic often coupled to Teradata semantics | Bounded MERGE/apply windows + staged apply |
| Concurrency planning | Workload management queues | Warehouse isolation + concurrency policies |
Examples
Illustrative Snowflake optimization patterns after Teradata migration: enforce pruning-friendly filters, bound MERGEs, isolate warehouses, and store baselines for regression gates.
-- Pruning-first query shape (avoid wrapping filter columns)
SELECT
region,
SUM(revenue) AS rev
FROM MART.FACT_ORDERS
WHERE EVENT_DATE BETWEEN DATE '2025-01-01' AND DATE '2025-01-31'
GROUP BY 1;Common pitfalls
- Carrying over PI/index thinking: expecting physical design to rescue query shape; Snowflake needs pruning-first predicates and evidence-driven clustering.
- Clustering by folklore: clustering keys chosen without evidence from predicates/join keys.
- Full-target MERGE: missing apply boundaries causes large scans and credit spikes.
- No warehouse isolation: BI and batch share warehouses; tail latency and spend spikes follow.
- Over-materialization: too many intermediates without controlling refresh cost.
- No regression gates: performance improves once, then regresses silently.
Validation approach
- Baseline capture: runtime, scan footprint, and credits for top queries/pipelines.
- Pruning checks: confirm pruning-friendly predicates and reduced scan footprint on representative parameters.
- Before/after evidence: demonstrate improvements in runtime and credit burn; document tradeoffs.
- Correctness guardrails: golden queries and KPI aggregates ensure tuning doesn’t change semantics.
- Regression thresholds: define alerts (e.g., +30% credits or +30% runtime) and enforce via CI or scheduled checks.
- Operational monitors: dashboards for warehouse utilization, credit burn, failures, and refresh SLA adherence.
Migration steps
- 01
Identify top cost and SLA drivers
Rank queries and pipelines by credits, runtime, and business criticality (dashboards, batch windows). Select a tuning backlog with clear owners.
- 02
Create baselines and targets
Capture current Snowflake metrics (runtime, credit burn, scan footprint) and define improvement targets. Freeze golden outputs so correctness doesn’t regress.
- 03
Tune layout and apply posture
Apply evidence-driven clustering where beneficial and redesign apply windows so MERGEs are bounded and pruning remains effective.
- 04
Rewrite for pruning and reuse
Apply pruning-aware rewrites, reduce repeated large scans with materializations where needed, and scope MERGEs to affected windows.
- 05
Warehouse posture and governance
Isolate batch and BI warehouses, tune concurrency, and implement guardrails to prevent credit blowups from new queries.
- 06
Add regression gates
Codify performance thresholds and alerting so future changes don’t reintroduce high credit burn or missed SLAs. Monitor post-cutover metrics continuously.
We identify your highest-cost migrated workloads, tune pruning and apply windows, and deliver before/after evidence with regression thresholds—so performance improves and stays stable.
Get an optimization backlog, bounded apply patterns, and performance gates (credit/runtime thresholds) so future releases don’t reintroduce slow dashboards or high credit burn.