CHAR/VARCHAR vs. NCHAR/NVARCHAR performance

CHAR/VARCHAR vs. NCHAR/NVARCHAR performance

Post by Feico de Boe » Sat, 26 May 2001 20:45:41



Hello folks,

I have a question regarding the performance impact that can be expected when
NLS/Unicode enabling an application. In this case it will require to modify
CHAR/VARCHAR columns into NCHAR/NVARCHAR. Apart from a Microsoft document
about internationalisation with some high-level remarks I couldn't find
anything 'on the net'.

Is there anybody out there with experience or pointers (URL's appriciated)
about this topic.

Many thanks.

Regards,

Feico de Boer.

 
 
 

CHAR/VARCHAR vs. NCHAR/NVARCHAR performance

Post by Mike » Sun, 27 May 2001 02:01:42


Since SQL Server 7 and 2000 natively support Unicode data I would not foresee a performance hit for using Unicode other than the expected hit of utilizing a data format that consumes more "space" to store and manipulate.

Since NT is natively Unicode, I would think any "hit" would be on using non-Unicode data types due to conversion costs.

Only issues in how the products were developed would cause any noticeable difference in performance.  For this you will likely need to test it yourself.  


Quote:> Hello folks,

> I have a question regarding the performance impact that can be expected when
> NLS/Unicode enabling an application. In this case it will require to modify
> CHAR/VARCHAR columns into NCHAR/NVARCHAR. Apart from a Microsoft document
> about internationalisation with some high-level remarks I couldn't find
> anything 'on the net'.

> Is there anybody out there with experience or pointers (URL's appriciated)
> about this topic.

> Many thanks.

> Regards,

> Feico de Boer.


 
 
 

1. data types nchar/nvarchar versus char and varchar

My understanding is that the nchar/nvarchar data types as opposed to char
and varchar predominently enable storage as unicode thus improving
internationalisation potential relative to code pages.

At a practical level..... the net result when saved as unicode is that twice
the amount of disc space is required.  Whilst disc space maybe not at a
premium nowadays are there any 'other' advantages to storing data as unicode
over and above the char and varchar data types for a local system of
moderate complexity.  Are we looking at substantial speed gains or is there
something else I have missed?

All and any comments welcome

Jim

2. Open INGRES/net v1.2 and ingres 6.4

3. When to use nvarchar/nchar, varchar/char, text/ntext

4. US-NJ: Lyndhurst-Centura Developer with Oracle and Web

5. CHAR/VARCHAR -> NCHAR/NVARCHAR

6. Problem with deleting rows in SQLS 6.5

7. Varchar vs Char vs nvarchar

8. Text datatype and indexes

9. nvarchar vs. varchar performance question

10. Char,VarChar,Text,NChar,NVarChar,Ntext

11. nchar vs. nvarchar for PK column datatype

12. nvarchar vs nchar

13. Q: Performance NCHAR - NVARCHAR