April 27, 2012 at 11:43 pm
Hi Friends,
I have Sql 2000. Since their a problem with unicode.
I have a doubt.whether Sql 2005/2008 will support unicode.
Problem arises with unicode is Unique key is Ariseing Error for when ever i insert an unicode data in that Constrain column........
Whether This problem will get solved in 2005/2008?
Any Experts is there to provide answer for this?
April 28, 2012 at 12:18 am
Can you post some more details, the DDL for the table in question, some test data and code that shows the problem, and the exact error message please?
There should be no problem with inserting unicode into an appropriately defined column, and it handles unique constraints on it just fine, so we need to see exactly what you are doing to understand your problem.
Mike
April 28, 2012 at 1:13 am
jbkumar03 (4/27/2012)
Hi Friends,I have Sql 2000. Since their a problem with unicode.
I have a doubt.whether Sql 2005/2008 will support unicode.
Problem arises with unicode is Unique key is Ariseing Error for when ever i insert an unicode data in that Constrain column........
Whether This problem will get solved in 2005/2008?
Any Experts is there to provide answer for this?
You should read the following links:
April 28, 2012 at 3:43 am
jbkumar03 (4/27/2012)
I have Sql 2000. Since their a problem with unicode.I have a doubt.whether Sql 2005/2008 will support unicode.
Why? All of these support unicode text provided they are stored correctly and you have the appropriate collation.
You also need to insert such characters like this.
INSERT INTO table (textcolumn) VALUES (N'??????')
INSERT INTO table (textcolumn) VALUES (N'Unicode spécifie un numéro unique' )
April 28, 2012 at 5:13 am
April 28, 2012 at 5:19 am
vinu512 (4/28/2012)
Sql Server 2005/2008 very well support Unicode. You just need to insert data correctly. Plus, you need to use data types like nvarchar for good performance.
You dont necessarily need nvarchar for performance. You do need Nvarchar and Nchar to store unicode.
The difference between the two will potentially save space depending on usage.
April 28, 2012 at 6:27 am
MysteryJimbo (4/28/2012)
vinu512 (4/28/2012)
Sql Server 2005/2008 very well support Unicode. You just need to insert data correctly. Plus, you need to use data types like nvarchar for good performance.You dont necessarily need nvarchar for performance. You do need Nvarchar and Nchar to store unicode.
The difference between the two will potentially save space depending on usage.
You can also store Unicode data using ntext. I was saying that using nvarchar is better than ntext.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply