Harish Mohanbabu <ha*****@msn.com> wrote in message news:<40*********************@news.frii.net>...
Hi,
I have got couple of questions about unicode settings for database and I
would be thankful if someone can clear the same for me. Here I go -
a. How can I find out whether unicode has been
initialised for an existing SQL Server database?
b. If unicode is initiated, would there be any difference
in performance? In particular, would there be any
performance degradation?
Thanks in advance,
Harish Mohanbabu
*********************************
Long way to go before I sleep ..
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
You don't mention which version of SQL Server you have, but 7/2000
supports Unicode data using the nchar/nvarchar/ntext data types. So if
you have columns in your tables of those types, they are capable of
holding Unicode data.
Unicode data types require double the amount of storage, so in some
cases they may be slightly slower - you need to move more data over
the network to return results, data and index pages will require more
space etc. But if you need to store Unicode data, then you need to use
those data types, so unless you have some specific performance issue,
there should be no reason to avoid them.
You may want to check out "Using Unicode Data" and "Collations" in
Books Online.
Simon
