Unicode - what''s the trend?
-
We have had a lot of development work lately, which resulted in several contract developers helping with the overflow. Now that is done and I have found a couple of databases where NVARCHAR, NCHAR are being used exclusively instead of VARCHAR and CHAR.
Have I missed a latest trend or something? We are a local U.S. company doing domestic work only. Is there some other reason that I should ditch my standard CHAR's for Unicode?
-
Nope. Stay with ANSI. It sounds as if the "helper" dbas used the defaults. There is no reason for you to be set up for UNICODE if you are strictly domestic.
Quand on parle du loup, on en voit la queue
-
It depends on who is using your applications and how they are using it. It also depends on what type of information you will be storing in those fields and how that data will be searched.
Personally, I would go with NVarChar and NChar and NText instead of their non-unicode data type equivalents. We do mostly domestic development but we have come across many instances where that company moved to another country and our application was already able to handle the non-ASCII text without issues. Even here in the US you have a chance of receiving data in a non-ASCII format so why not be prepared for it.
Just my 2cents worth.
SJ
-
Move from varchar to Nvarchar will increase data size by 100% and that will bring other performance and hardware considerations.
AlexM
Accepting all invitesViewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply