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.