Skip to contentSkip to navigationSkip to topbar
Twilio Segment Docs
Page tools
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Redshift Reverse ETL Setup

Set up Redshift as your Reverse ETL source.

(information)

Redshift Reverse ETL sources support Segment's dbt extension

If you already use dbt with a Git repository, you can use Segment's dbt extension to centralize model management and versioning, reduce redundancies, and run CI checks that prevent breaking changes.

To set up Redshift with Reverse ETL:

  1. Log in to Amazon Redshift(link takes you to an external page) and choose the Redshift cluster you want to connect to Reverse ETL.

  2. Follow the networking instructions to configure the required network and security settings.

  3. Run the following SQL commands to create a user named segment.

    1
    -- Create a user named "segment" that Segment will use when connecting to your Redshift cluster.

    2
    CREATE USER segment PASSWORD '<enter password here>';

    3
    

    4
    -- Allows the `segment` user to create new schemas on the specified database. (this is the name you chose when provisioning your cluster).

    5
    GRANT CREATE ON DATABASE "<enter database name here>" TO "segment";

    6
    

    7
    -- Create Segment schema.

    8
    CREATE SCHEMA __segment_reverse_etl;

    9
    

    10
    -- Allow user to use the Segment schema.

    11
    GRANT USAGE ON SCHEMA __segment_reverse_etl TO segment;

    12
    

    13
    -- Grant all privileges on all current tables in the Segment schema.

    14
    GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA __segment_reverse_etl TO segment;

  4. Follow the steps in Add a source to finish adding Redshift as your source.

Extra permissions

extra-permissions page anchor

Give the segment user:

  • Read permissions for any resources (databases, schemas, and tables) the query needs to access.
  • Write permissions for the Segment managed schema (__segment_reverse_etl), which keeps track of changes to the query results.

Troubleshooting

troubleshooting page anchor

Extraction failures: relation doesn't exist

extraction-failures-relation-doesnt-exist page anchor

If the query runs successfully in the Query Builder, but the sync fails with a relation does not exist error, confirm that the schema name is included before the database table name, and check that the schema name is correct:

SELECT id FROM <schema_name>.<table_name>

After you've successfully added your Redshift source, add a model and follow the remaining steps in the Reverse ETL setup guide.