We receive data from a 3rd party, the flat file is correct in that it contains the right characters in the file
Flat file data
Emplea la calculadora como instrumento de exploración y verificación de resultados
Emplea la calculadora como instrumento de exploraciÃ³n y verificaciÃ³n de resultados
I changed the collation at the column to Latin1_General_BIN and Modern_Spanish_BIN, reimported the data, but still the data is showing with the Ã³ instead of ó (it is also doing it for other characters).
The data that we receive is a mixture of English and Spanish (Mexican).
What would be the best collation for the import so that it stores the ó and not the Ã³, would of thought a binary collation but doesnt seem that way?
Thanks in advance.
Edit, the column is NVARCHAR already, but the file is not unicode, if I try to change to unicode in the SSIS package it doesnt recognise the columns any more.
Edit 2 - got to be the file not being in unicode, inserted the value manually for a number of collations and came back as it should for all collations tried, now to try and convert the flat file to unicode before import as it is already doing a data conversion on the import and still not generating the right output.
How to post data/code for the best help - Jeff ModenNeed a string splitter, try this - Jeff ModenHow to post performance problems - Gail ShawManaging Transaction Logs - Gail ShawTroubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger