You want to migrate your existing Teradata data warehouse to BigQuery. You want to move the historical data to BigQuery by using the most efficient method that requires the least amount of programming

Question

Options

• AUse BigQuery Data Transfer Service by using the Java Database Connectivity (JDBC) driver with FastExport connection.
• BCreate a Teradata Parallel Transporter (TPT) export script to export the historical data, and import to BigQuery by using the bq command-line tool.
• CUse BigQuery Data Transfer Service with the Teradata Parallel Transporter (TPT) tbuild utility.
• DCreate a script to export the historical data, and upload in batches to Cloud Storage. Set up a BigQuery Data Transfer Service instance from Cloud Storage to

• A
  76% (34)
• B
  13% (6)
• C
  4% (2)
• D
  7% (3)

Explanation

Option A is correct because BigQuery Data Transfer Service (DTS) with the JDBC driver and FastExport connection streams data directly from Teradata to BigQuery - no intermediate local storage is required, satisfying the limited-space constraint - and it operates as a managed service, minimizing the amount of custom code you need to write.

Option B fails on both constraints: TPT export writes data to local disk first (consuming the scarce local storage) and requires you to write and manage the export script plus the bq import steps.

Option C is a common trap - TPT's tbuild utility stages data locally before transfer, which again hits the local storage limit, and it involves more manual configuration than the fully managed JDBC/FastExport path.

Option D is the most work: it requires a custom export script, manual Cloud Storage uploads in batches, and a separate DTS instance - all while needing local staging space for the exported data.

Memory tip: Think of FastExport + JDBC = "pipe directly to BigQuery" - the word Fast hints that it bypasses local disk and streams data, making it both storage-friendly and low-code via the managed DTS service.

No community discussion yet for this question.