To start using Redshift as a Supermetrics destination, some requirements need to be met. These prerequisites ensure that a working connection can be set up to successfully transfer data to your Redshift data warehouse.
Database and schema
You need a Redshift cluster, database, and schema in place before you can create a Redshift destination for Supermetrics. Learn more about Redshift in its documentation.
Managing schema changes
When you're setting up your schemas, it's important to remember that Supermetrics has the ability to make schema changes to your tables in Redshift. These are generally only triggered by a schema change initiated by you or someone in your Supermetrics team using the Query Manager.
To make sure that Redshift is properly equipped to handle these schema changes, ensure that your database follows these guidelines:
- Don't use views with schema binding
- By default, Redshift views have schema binding enabled. This means that tables referenced by these views can't be dropped or undergo schema changes. We recommend ensuring that any views that have been created to reference tables created by Supermetrics use the WITH NO SCHEMA BINDING clause in the view definition. Learn more about this in Redshift's documentation on late-binding views.
- Don't enforce key constraints
- Key constraints can get in the way of schema changes. We recommend removing any key constraints on the tables so that schema migration can go ahead without error. Learn more about key constraints in Redshift's documentation.
You'll need a Redshift user with permissions CREATE and USAGE on the schema you want to send data to, and the password corresponding to that user.
You’ll need to allowlist select IP addresses if your organization only allows access from “selected networks”. Add the IP addresses listed here to your cluster’s Inbound Rules in its VPC security group. Don’t forget to include your own IP address.
Navigate to Clusters → Properties → Network and security settings → listed VPC security group → Edit Inbound Rules to add the IP addresses. Don't forget to include your organization's own.
<Your organization's IP address>