This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
If it is the same DSN within ODBC for both, there shouldn’t be a difference; but Alteryx does make assumptions about the character set based on column width/type. There is a way to override this by modifying the DSN through ODBC Manager; but if you’re using the same entry there’s no point in risking a change that could have unintended consequences to SQLA. Instead, I’d recommend to first try using the formula: ConvertToCodePage([FieldName],28592). If that isn’t the right codepage, in the Help pages, search “Codepage”. There’s a listing of all of the character sets you can convert to/from.