Not so cool beans, we've been running this on another server for further testing and we've now experienced same behaviour. Not convinced this is memory related if I'm honest. Bumping this again, has anyone seen such behaviour before? SQL returning alternative characters to what should be returned from both SSIS and SSMS??

Just don't get this...