varchar 和 nvarchar SQL Server 数据类型之间的主要性能差异是什么? [英] What are the main performance differences between varchar and nvarchar SQL Server data types?

问题描述

我正在使用 SQL Server 2005 为我学校的小型 Web 应用程序开发数据库.
在 varchar 与 nvarchar 的问题上，我看到了一些思想流派:

I'm working on a database for a small web app at my school using SQL Server 2005.
I see a couple of schools of thought on the issue of varchar vs nvarchar:

1. 使用varchar，除非你处理大量国际化数据，否则使用nvarchar.
2. 只需使用 nvarchar 即可.

1. Use varchar unless you deal with a lot of internationalized data, then use nvarchar.
2. Just use nvarchar for everything.

我开始看到视图 2 的优点.我知道 nvarchar 确实占用了两倍的空间，但这不一定是一个大问题，因为它只会存储几百个学生的数据.对我来说，最简单的方法是不要担心它，只允许所有内容都使用 nvarchar.还是我遗漏了什么?

I'm beginning to see the merits of view 2. I know that nvarchar does take up twice as much space, but that isn't necessarily a huge deal since this is only going to store data for a few hundred students. To me it seems like it would be easiest not to worry about it and just allow everything to use nvarchar. Or is there something I'm missing?

推荐答案

始终使用 nvarchar.

Always use nvarchar.

对于大多数应用程序，您可能永远不需要双字节字符.但是，如果您需要支持双字节语言并且您的数据库模式中只有单字节支持，那么返回并修改整个应用程序的成本确实很高.

You may never need the double-byte characters for most applications. However, if you need to support double-byte languages and you only have single-byte support in your database schema it's really expensive to go back and modify throughout your application.

将一个应用程序从 varchar 迁移到 nvarchar 的成本将远远高于您在大多数应用程序中使用的一点点额外磁盘空间.

The cost of migrating one application from varchar to nvarchar will be much more than the little bit of extra disk space you'll use in most applications.

这篇关于varchar 和 nvarchar SQL Server 数据类型之间的主要性能差异是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！