Where can I configure (if it's possible) how Sql Server 2005 "interprets" character encoding of string data sent trough TDS protocol (in this case from web application)?
Maybe it would be better if I describe whole problematic situtation:
- when inserting regional characters such as: ą, Ą, ć, Ł, ź (and so on - polish regional characters), trough TDS protocol - "INSERT INTO" query from web application, they appear in mssql table as: a (instead of ą), A (instead of Ą), c, L, z etc.
- target column type is nvarchar(MAX)
- I looked at data sent "trough wire" (with WireShark) and all data is sent using UTF-16 encoding, which looks ok: for example Ą is sent as U+0104.
- when inserting same string into local database instance (Microsoft SQL Server Express Edition) it works fine, but on remote host (in customer location - it is Microsoft SQL Server Standard Edition 64-bit) this "de-regionalization" occurs. That why I suppose it is all about SQL Server configuration, because the only difference from web application side is choosing other sql server (so TDS drivers, configuration, conbection settings and so on are the same).
I hope someone could help me with this one.