Re: Data Type nvarchar or varchar

Thanks a lot Sylvain,

I'm thinking to change only to save space.
It´s true, until kmow, using nvarchar I neever had problems.
By another side, I think if varchar also doesn´t bring problems, probably is
good to change the datatype.

Thanks

I
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
escreveu na mensagem news:eK4y3dHMJHA.1160@xxxxxxxxxxxxxxxxxxxxxxx
Portuguese has diacritical symbols in its alphabet, so you need to use a
code page if you want to go the ASCII road. Everytime you use a code
page, there is always a possibility that you will have problem if your
data is to be access by a machine which doesn't use the exact same code
page; so for example someone who is greek, russian, chinese or even
french - whose alphabet is close but not identical to the portuguese -
will have problem accessing or updating your data.

If I were you, I would stop bothering myself and Unicode. There is alreay
enough problems in life so that you don't really have the need (or the
luxury) to add more to it. You database was already running fine in
Access with Unicode, why would you want to start changing things now?

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"Jose" <perdijc@xxxxxxxxxxx> wrote in message
news:%23F5lHLGMJHA.2348@xxxxxxxxxxxxxxxxxxxxxxx
My data is enghish or portuguese, so, is derived from latin language.

Do you think can i change nvarchar to varchar without impact problems?
Thanks,
Jose
"Scott Lichtenberg" <donot@xxxxxxxxx> escreveu na mensagem
news:e2FWfkFMJHA.2036@xxxxxxxxxxxxxxxxxxxxxxx
nvarchar supports Unicode data. Functionally, it's the same as varchar,
but it may require additional storage - I think Unicode requires two
bytes per character instead of one - but I could be wrong. If your data
is always going to be English (or a similar ASCII based language) you
can switch the data types back to varchar.


"Jose" <perdijc@xxxxxxxxxxx> wrote in message
news:eVHbQjEMJHA.3688@xxxxxxxxxxxxxxxxxxxxxxx
When we use upgrade wizard to migrate ms access to sql server, the
fields data type text is converted to nvarchar.
My question is, Can I change nvarchar to varchar? These changes does it
not affect nothing?

Thanks

JCP









.

Relevant Pages

  • Re: Unicode
    ... NVARCHAR is used to store unicode values and VARCHAR for non-unicode data. ... "Ramesh" wrote in message ...
    (microsoft.public.sqlserver.programming)
  • Re: JDBC - varchar or nvarchar fields?
    ... Essentially if your not storing multilingual data use varchar, as nvarchar ... (considering that Java internally works in unicode too)? ...
    (comp.databases.ms-sqlserver)
  • Re: Beginners question
    ... Varchar will be half the size. ... > fields were converted to nvarchar data type in SQL Server by default. ... > varchar and nvarchar except that nvarchar is Unicode Character data type. ...
    (microsoft.public.sqlserver.programming)
  • Re: varchar and nvarchar, which one to use???
    ... > and i was confused the correct use of varchar and nvarchar. ... For a business like Amazon, the choice should be simple: ... have a customer that requires support for, say, Polish and Swedish the same ...
    (microsoft.public.sqlserver.programming)
  • varchar and nvarchar, which one to use???
    ... and i was confused the correct use of varchar and nvarchar. ... I've been using varchar in the past, but i noticed all the code samples ... what's the best practice using these data types? ... nvarchar literal together with an indexed varchar column, ...
    (microsoft.public.sqlserver.programming)