Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT> fter upgrading the redshift connector to 4.0.2, is it safe to get rid of the airbyte_internal schema?

Yes, it is safe to drop the old `airbyte_internal` schema (and its raw tables) after upgrading to Redshift destination v4.0.0+, *provided you verify your data first*.

As of version 4.0.0, the Redshift destination was fully rewritten to use the <https://docs.airbyte.com/platform/using-airbyte/core-concepts/direct-load-tables|Direct-Load> paradigm. Raw tables (`_airbyte_raw_*`) are *no longer created or used* — data is written directly to final tables. [<https://docs.airbyte.com/integrations/destinations/redshift#output-schema|Redshift output schema>]

The official migration guide recommends these steps: [<https://docs.airbyte.com/integrations/destinations/redshift-migrations|Redshift migration guide>]

1. Confirm that raw tables (`_airbyte_raw_*`) are no longer being produced by the new connector.
2. Upgrade the destination to version 4.0.0 (or later, such as 4.0.2).
3. *Verify data in the final tables* to ensure everything looks correct.
4. Optionally drop the old raw tables / `airbyte_internal` schema after verification.
*Before dropping, make sure:*
• You are not running any downstream dbt models or SQL queries that still reference the old raw tables or the `airbyte_internal` schema.
• All your syncs have completed successfully at least once with the new version.
If you've confirmed the above, dropping the `airbyte_internal` schema is safe and will free up storage space. :thumbsup: 0 button :thumbsdown: 0 button :information_source: *Tip:* Mention *@kapa.ai* in the thread for follow-ups or *DM the app* for *1-to-1* help.