I am attempting to create a couple of new ETL process that use ODBC sources. I have found that the CHAR and VARCHAR fields are being interpreted as NCHAR and NVARCHAR data types in SSIS, but the same ODBC source in DTS results in the desired CHAR and VARCHAR interpreted fields. Since the destination tables require the CHAR and VARCHAR, I have to manually convert each field in the Data Flow for SSIS, adding development time that would not exist in the DTS package. The option of updating the destination to UNICODE has been shot down and I'm trying to perform all new ETL development in SSIS.
My question then becomes, is there are a way to force SSIS to interpret the metadata the same way as DTS in order to eliminate the additional conversions?