title: Determine What Unicode Characters SSIS Won't Handle
body: <p>I'm working with a SSIS package that takes data from SQL Server and creates text files to ship to a vendor. Currently the files are being encoded using ANSI 1252 and the Unicode checkbox is not checked on the Flat File Connection Manager.</p>
  
  <p>The package failed when it encountered this symbol: ♥</p>
  
  <p>This led me to believe that if the step attempted to write out any non-ascii character, it would fail. However, it will succesfully handle: "ş" by converting it to a standard "s". For our purposes, this behavior is great, and if it did something similar to the heart symbol, there would be no issue. I'm trying to avoid sending a Unicode file, as the file is already very large and doubling its size is not preferable.</p>
  
  <p>What I'm looking for is the range of unicode characters that SSIS will not automatically convert for me. Then what I'll need to do is a replace on the original SQL statement, to clear out those characters like the ♥.</p>
  
  <p>We started with <code>REPLACE(NAME, SUBSTRING(NAME, PATINDEX('%[^ -ÿ]%', NAME COLLATE Latin1_General_BIN2), 1), '')</code>, but this will replace the "ş" with a space, which we are attempting to avoid since SSIS handles the "ş" just fine.</p>
  
  <p>Thanks for reading this question!</p>