Skip to main content
The Teradata target connector powers your analytical environments by leveraging Teradata’s MPP parallelization and optimization features.

​
Prerequisites

  • Accounts and roles: a Teradata user with CREATE TABLE, INSERT, UPDATE, DELETE privileges and access to the TPT utility when used.
  • Infrastructure: network connectivity between Popsink and the Teradata port (1025 by default) with TLS encryption enabled; supported versions are Vantage 17.x and later.
  • Capacity and quotas: sufficient AMP allocation to absorb write spikes, session limits sized for Popsink jobs, and appropriately dimensioned permanent/swap space.
  • Monitoring: access to the DBC.ResUsage* views and DBC.QryLog to collect performance and error metrics.

​
Configuration

  • Batch loads
  • Continuous flows
1

Declare the target

Enter the host, system (DBCName), and database name in Popsink. Attach a secret containing the service account and, if required, the client certificate.
2

Choose the write mode

Select the TPT utility for large volumes or FastLoad for empty tables. Configure the block size (blocksize) and errorlimit level.
3

Optimize batches

Configure the primary key or secondary indexes, enable multivalue compression, and define the automatic restart policy for failures.

​
Monitoring

  • Track CPU and I/O usage through DBC.ResUsageScpu and DBC.ResUsageSvpr, complemented by Popsink metrics (throughput, retries, latency).
  • Configure alerts when 2689 (duplicate row) or 2641 (AMP down) errors exceed a defined threshold.
  • Retain TPT and FastLoad logs to simplify diagnostics if a job aborts.

​
Best practices

  • Partition large tables with PRIMARY INDEX values aligned to the distribution key.
  • Order columns to maximize block-level compression.
  • Align Teradata maintenance windows with Popsink schedules to avoid collisions.
Disable the CHECKPOINT OFF option only for exceptional jobs: without a recovery point, restarting a large load can severely impact production.

​
FAQ

Enable the Popsink upsert option or add a staging step with deduplication before the final insert.
Pause the job, work with the DBA team to restore the AMP, then restart the connector once the cluster state is validated.
Use DBC.QryLog to trace executed queries and export Popsink logs to your centralized SIEM solution.

Monitor targets

Configure dashboards to track the health of Teradata and other destinations.

Alerting Popsink

Receive alerts when TPT or FastLoad jobs fail.

Pipeline examples

Reuse a reference pipeline to accelerate your Teradata deployments.