Redshift Migration Guide
This version removes support for standard inserts. Although this loading method is easier to set up than S3 staging, it has two major disadvantages:
- Standard inserts is significantly slower
- Standard inserts is significantly more expensive
Redshift's documentation states:
We strongly encourage you to use the COPY command to load large amounts of data. Using individual INSERT statements to populate a table might be prohibitively slow.
See our Redshift docs for more information on how to set up S3 staging.
This version introduces Destinations V2, which provides better error handling, incremental delivery of data for large syncs, and improved final table structures. To review the breaking changes, and how to upgrade, see here. These changes will likely require updates to downstream dbt / SQL models, which we walk through here. Selecting Upgrade will upgrade all connections using this destination at their next sync. You can manually sync existing connections prior to the next scheduled sync to start the upgrade early.
Worthy of specific mention, this version includes:
- Per-record error handling
- Clearer table structure
- Removal of sub-tables for nested properties
- Removal of SCD tables
Learn more about what's new in Destinations V2 here.