Skip to main content
Scenario: copy public.orders from an application PostgreSQL database into analytics.orders_live in a reporting PostgreSQL database.

Before you begin

Have source and destination PostgreSQL credentials ready. The source user needs read access to public.orders; the destination user needs write access to analytics.orders_live.

1. Create connections and pipeline

  1. Open Connections and create/test a PostgreSQL Source connection.
  2. Create/test a PostgreSQL Destination connection.
  3. Open Data Pipelines, click New Pipeline, enter a name, select the source connection, and create the pipeline.
  4. Open the new pipeline. It opens in the tabbed pipeline workspace.

2. Configure Source

  1. Open Source.
  2. Click Test connection.
  3. Click Discover catalog.
  4. Enable public.orders.
  5. Keep Full table for the first run.
  6. Click Preview and inspect the rows.
  7. Click Save stream settings.

3. Add a destination

  1. Open Destinations.
  2. Click Add destination.
  3. Choose the destination connection, enter a display name, and set the target schema to analytics.
  4. Click Save destination.

4. Create and publish a transformation

  1. Open Transformations and select the new destination.
  2. Click New transformation.
  3. Enter a name, stable key, output model, and select public.orders as input.
  4. Use this SQL:
  1. Click Save draft.
  2. Click Validate draft.
  3. Click Preview output and inspect the result.
  4. Click Publish revision and confirm.

5. Assign the output target

  1. Return to Destinations and open the destination.
  2. Under Published output targets, set the table to analytics.orders_live.
  3. Set the Upsert key to id.
  4. Click Create or verify destination table when appropriate, then Save destination.

6. Validate and run

  1. Open Overview.
  2. Click Validate pipeline and resolve any incomplete readiness check.
  3. Click Run all in the header.
  4. Open Runs, select the execution, and confirm the destination, published revision, rows written, duration, and success status.

Add automation later

After a manual run succeeds, open Settings. Choose a fixed 1–24 hour interval or enter a five-field UTC cron expression, save the schedule, and keep the pipeline active.