Start with a representative workload
Use this guide to prepare a Teradata to BigQuery assessment. The first decision is whether the intended target preserves the behavior your business relies on, at an acceptable operating cost.
What to collect from Teradata BTEQ and SQL
- Include BTEQ scripts, SQL, macros, and the surrounding load/export orchestration.
- Sample volatile tables, QUALIFY, vendor-specific functions, and BTEQ error branching.
- Capture distribution assumptions, transaction behavior, and runtime baselines for the most demanding queries.
Plan the BigQuery implementation
Agree which transformations run in BigQuery SQL and which need a separate Python or Spark runtime. Check query cost, partition pruning, permissions, and load/retry behavior.
Agree what a passing result means
- Fix the baseline. Use the same input snapshot and record source parameters and expected outputs.
- Compare the data. Check row counts, keys, duplicates, nulls, aggregates, and row-level values with agreed precision tolerances.
- Review exceptions. Keep a list of behavior that needs manual work, an owner, and a repeatable test.
- Check operations. Measure runtime and cost, rehearse retries and recovery, and confirm who owns the production job.
What to decide after the pilot
Review generated code, test results, unresolved exceptions, and measured delivery effort together. Expand only after the sample meets your acceptance criteria. Agree whether your team leads the next wave, needs engineering support, or wants managed delivery.
Review a sample from your estate
Request a free assessment to agree a representative sample and target. We will follow up with the code-transfer steps; this is not an instant upload.