dj,
Well it takes up twice as much space, so yes. I.e. if you are joining on
a nvarchar column it will take longer. I/O requests will take longer
because you will half as much data on a page, therefore you will need
twice as many I/Os.
Each character in a unicode field requires 2 bytes to store it.
--
Mark Allison, SQL Server MVP
<a rel="nofollow" style='text-decoration: none;' href="http://www.markallison.co.uk" target="_blank">http://www.markallison.co.uk</a>
Looking for a SQL Server replication book?
<a rel="nofollow" style='text-decoration: none;' href="http://www.nwsu.com/0974973602.html" target="_blank">http://www.nwsu.com/0974973602.html</a>
dj wrote:
> Does the datatype nvarchar affect query performance in a
> negative way as opposed to simply using varchar?
>> Stay informed about: using nvarchar