|
Home > Archive > MS SQL Server > June 2005 > Performance impact when switching from US English to Chinese PRC l
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Performance impact when switching from US English to Chinese PRC l
|
|
| bsanders 2005-06-29, 8:23 pm |
| I just recently migrating a legacy MSSQL 2000 database (containing Simplified
Chinese GBK double-width characters) from varchar data_type to nvarchar using
DTS, which in the process requires me to switch the Windows 2000 US English
locale to Chinese PRC locale.
All these are to allow me to display Chinese characters on the web page
using ASP.NET. Everything went on successfully, however, I notice a
significantly performance drop when doing SQL queries now, whereby it is
using up more CPU for each SQL query.
I wonder if this is expected?
| |
| David Gugick 2005-06-29, 8:23 pm |
| bsanders wrote:
> I just recently migrating a legacy MSSQL 2000 database (containing
> Simplified Chinese GBK double-width characters) from varchar
> data_type to nvarchar using DTS, which in the process requires me to
> switch the Windows 2000 US English locale to Chinese PRC locale.
>
> All these are to allow me to display Chinese characters on the web
> page using ASP.NET. Everything went on successfully, however, I
> notice a significantly performance drop when doing SQL queries now,
> whereby it is using up more CPU for each SQL query.
>
> I wonder if this is expected?
The unicode character columns are going to require double the amount of
storage over their non-unicode counterparts. Depending on how those
columns are used within your queries or indexes, there could be an
impact because of the decreased row density. You'll have to provide
additional information about the tables, indexes, and queries in
question.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com
|
|
|
|
|