470,575 Members | 1,880 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,575 developers. It's quick & easy.

To unicode or not?

SQL Server 2005 64-bit 9.00.3042 SP2

I am migrating a database to SQL Server that is not unicode...

Assuming that I have no plan to store different languages (other
than English), does it make sense to change my char() -nchar()
and my varchar() -nvarchar()?

My collation is sql_latin1_general_cp1_ci_as. Is there any relationship
between the collation and unicode support? I see that I can alter
existing columns, changing from char -nchar. So I could go unicode
later, yes? Is this a good idea?

If I go unicode, am I asking for trouble from other tools/protocols that
access the database, like JDBC/ODBC? If something knows about/supports
varchar(), will it also automatically know about/support nvarchar()?

Any thoughts appreciated.


Oct 24 '08 #1
0 1148

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Michael Weir | last post: by
8 posts views Thread by Bill Eldridge | last post: by
8 posts views Thread by Francis Girard | last post: by
4 posts views Thread by webdev | last post: by
2 posts views Thread by Neil Schemenauer | last post: by
10 posts views Thread by Nikolay Petrov | last post: by
6 posts views Thread by Jeff | last post: by
13 posts views Thread by Tomás | last post: by
24 posts views Thread by ChaosKCW | last post: by
1 post views Thread by livre | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.