Re: Microsoft SQLServer - varchar or nvarchar fields?
- From: "joeNOSPAM@xxxxxxx" <joe.weinstein@xxxxxxxxx>
- Date: 11 May 2006 07:03:03 -0700
The N'xxxxx syntax would be redundant but not harmful. It
just means that the data in nvarchar, and if the driver is
sending strings as unicode (all MSSQL JDBC drivers do
this by default), it is unnecessary for prepared statement
parameter values. For constants it might be good.
The performance issue is as I described. The huge performance
problem comes by mismatching varchar with nvarchar. If you
stick to one, there is no problem. I believe the amount of
space taken up by nvarchar compared to varchar is a minimal
disk space issue only. Because your app. is multilingual, I
can't imagine a reason you'd continue to consider varchar.
Joe
.
- References:
- Microsoft SQLServer - varchar or nvarchar fields?
- From: D.
- Re: Microsoft SQLServer - varchar or nvarchar fields?
- From: joeNOSPAM@xxxxxxx
- Re: Microsoft SQLServer - varchar or nvarchar fields?
- From: D.
- Microsoft SQLServer - varchar or nvarchar fields?
- Prev by Date: Re: Microsoft SQLServer - varchar or nvarchar fields?
- Next by Date: Re: General Error - can I do better than that.
- Previous by thread: Re: Microsoft SQLServer - varchar or nvarchar fields?
- Index(es):
Relevant Pages
|
|