We now truncate LOCALDATETIME values to microsecond precision before we load them as TIMESTAMP values to your Redshift destination. For example, if we receive a LOCALDATETIME value
2021-02-01T15:24:47.1234567, we truncate the value and write it to your destination as
We have added a new test in the Redshift destination setup form to verify CREATE TEMPORARY TABLES permissions. When you set up your Redshift destination, you must grant the
fivetran user permission to create temporary tables in your Redshift warehouse. To learn how, see our Redshift setup guide.
- Fivetran no longer performs
VACUUM DELETEfor your Redshift warehouses on the weekends, because Redshift now does it automatically. For more information on how Amazon Redshift schedules the
VACUUM DELETEoperation, check out Amazon’s changelog.
For the following warehouses, Fivetran now drops the
primary_key field from existing tables in your warehouse if there is a
primary_key coming in from your data source:
- SQL Server
We no longer sync system columns, such as
oid, to your Redshift warehouse.
We have changed the way we reclaim disk space from deleted rows. You can find additional details in our Redshift documentation.