>I have a database on the Universal Thread site which I need to adjust a setting so to support extended characters. Presently, there are close to two millions records in it. On the structure, I have a Text field to hold the message. I need to adjust the that field so it will support extended characters such as Cyrillic. However, we need to make sure we do not change the existing data. Once this setting will be done, we need to assure the support of actual messages so as the ongoing support of upcoming messages. SQL Server allows us to stamp more than one codepage into a field. If that is correct, I would need some advice here as to what I have to do to respond to that request.
>
>The problem we have now is as soon as someone enters some Cyrillic text in a message, for example, it appears ok on the preview. This works because the data is taken as is from the browser. But, once the data is saved, it is convered into ????????????? in the database. How can I adjust the database for that particular field so we can support all those foreign languages?
I believe you need to use nvarchar(max) instead of the text. Try to add nvarchar(max) field to the tables and update it with the content of the current text field. Then you may start testing entering values into this field. Once you switch to nvarchar(max) it should work as expected with different languages.
If it's not broken, fix it until it is.
My Blog