I've got a web app that doesn't mind the users inputting their address information in unicode data.
A SSIS package of mine used that data to generate exports to another provider. That package never had a problem until this past weekend.
The error the package returned was"text was truncated or one or more characters had no match in the target code page".
I found a lot of solutions where people setup a function you can pass the field to and it would parse out any of this garbage and clean it out. They seemed overly complex.
My solution was to change the view. In the view I cast the nvarchar(40) into a varchar(40). Since the package was expecting an nvarchar I then cast that output back to nvarchar(40) to save me the headaches of replacing the package. (I've done very little, self taught, SSIS work) Then I run a replace on the field and...