Hello
This might be painfully obvious to some (most?) of you, however it has been bugging me for a while now.
I have two databases running on the same SQL server (2005). As far as I can see they both have the same language/regional properties. Both have collation set to "Sloveninan_CL_AS" and yet one stores all Slovenian special characters (č, ž, š) without a problem, and the other coverts them to their non-regional sensitive "matches" (c, z, s).
All strings subjected to regional characters in both databases are stored in fields of the same type (varchar).
I am wondering what other settings are there that could affect this behaviour? What additional steps can I take to ensure special characters will be saved correctly in the second database?
EDIT: The only additional information that could prove relevant I can think of is that the second ("malfunctioning") database was initially created with a different collation setting and was changed at a later time, whereas the first was (probably) created with the setting set to the current value. However I think, since the setting can be changed, this shouldn't be a problem. Also, the server has been restarted since the collation setting was changed.