Re: VarChar VS. nVarChar

Heh, well, I guess if the things I'm trying to figure out now are things that "experts" have conflicting ideas about, then I must finally be starting to pick this stuff up. :-)

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com


"Jay" <-> wrote in message news:%23%23sUAOwUIHA.3556@xxxxxxxxxxxxxxxxxxxxxxx
This may be a bit dated, but in my "Inside SQL Server 7.0" book (1999) it
strongly advises using the least amount of storage in a row. The less you
store, the more rows you can fit in a page, so the fewer disk accesses you
need - these are the things that take time.

"Andrew Backer" <awbacker@xxxxxxxxx> wrote in message
news:67f4065d1d35a8ca20c2beb695ef@xxxxxxxxxxxxxxxxxxxxx
Unless I was working on a really memory constrained system I would use
NVarChar.
And if the system was that memory constratined, i probably wouldn't be
using
SQL Server. So far I have never used varchar other than when I needed the
extra size for something, just to e safe, and didn't want the hastle of
dealing
with 'text' and 'ntext' types. DB stored html pieces is one case.

If you have too much data then you could just use varchar, but I doubt that
is actually the case for you. Just think, with these damn 64 bit machiens,
all our ints are going to double in size too :(

Go with nvarchar unless there is a real reason not to.

// Andrew

I'm just curious how many people use the Unicode string types for
their data.

At this stage, it doesn't seem needed and takes up about twice the
storage. Am I better off using nVarChar, or is VarChar just fine?

Thanks.




.

Relevant Pages

  • Re: VarChar VS. nVarChar
    ... I am not overly worried about storage, personally, as storage is cheap. ... Gregory A. Beamer ... Am I better off using nVarChar, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: VarChar VS. nVarChar
    ... Unless I was working on a really memory constrained system I would use NVarChar. ... So far I have never used varchar other than when I needed the extra size for something, just to e safe, and didn't want the hastle of dealing with 'text' and 'ntext' types. ... Just think, with these damn 64 bit machiens, all our ints are going to double in size too:( ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Data Type nvarchar or varchar
    ... Access with Unicode, why would you want to start changing things now? ... Do you think can i change nvarchar to varchar without impact problems? ... can switch the data types back to varchar. ...
    (microsoft.public.access.adp.sqlserver)
  • 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)