Issues when loading data in Snowflake and Amazon Redshift

Loading data from a table in MS SQL Server with binary TIMESTAMP column

MS SQL Server binary TIMESTAMP and ROWVERSION columns are automatically converted to LONG. It is, however, important to change the field data type to BIGINT in mapping because, by default, binary TIMESTAMP fields are mapped to the TIMESTAMP data type. 

Column type 'VALUE' is not recognized

Example: Timestamp 'WEB' is not recognized.

This is most likely caused by incorrect order of fields in the file to load.

Solution: enable "Reorder columns to load to match order of columns in the target table." under Mapping/Parameters/Handling schema changes.

End of record reached while expected to parse column "COLUMN NAME"

This is most likely caused by the presence of special characters in the data which prevents Snowflake or Redshift from parsing the generated CSV file.

To fix, modify the CSV format as following:

1. Set "Enclosure Character" to "

2. Enable "Always Enclose"

3. Enable "Escape double-quotes"