Having played around for a couple of hours I'm fairly sure this is all about data types Unicode / Non Unicode and the way that SSIS guesses types. A fairly reliable workaround seems to be to use a SQL statement which explicitly casts a column to the required type rather than taking the data the way it comes.
Having played around for a couple of hours I'm fairly sure this is all about data types Unicode / Non Unicode and the way that SSIS guesses types. A fairly reliable workaround seems to be to use a SQL statement which explicitly casts a column to the required type rather than taking the data the way it comes.