从区分大小写映射到不区分大小写现在看来是很微不足道的，但实际上很难有效地进行这一映射。
Now it would seem fairly trivial to map from case-sensitive to case-insensitive, but in fact it's hard to do it efficiently.
用户名称和密码都是区分大小写的。
如果您不再想在这个表格的任何一个域上激活不能区分大小写查询程序，您可以使整个表格的索引功能失效。
If you no longer want to enable case-insensitive queries on any field in the table, you can disable indexes for the entire table.
在不区分大小写的数据库中，这种查询花费的时间增加了5%到8%。
Such queries took 5% to 8% longer in the case-insensitive database.
区分大小写：对单词的字母大小写进行搜索（默认是忽略字母大小）
Case sensitive : search is performed with respect to the letter-case of the words (default is to ignore letter-case)
如果Samba以大小写无关的方式访问它们，则无法区分这两个文件。
If Samba doesn't use case-sensitive access, then it is unable to differentiate between the two files.
缺省情况下，该比较是区分大小写的，这意味着inetorgperson和inetorgperson将被视为不同的类。
By default, the comparison is case sensitive, which means that inetorgperson and inetorgperson are treated as different classes.
您可以使用-iname覆盖区分大小写的匹配，并且您可以使用- follow根据符号链接进行遍历。
You can override case-sensitive matches with -iname, and you can traverse symbolic links with -follow. Here's an example that applies both options.
这条命令将会搜索所有名字里包含“searchstring”的文件和文件夹，而- i意味着搜索是不区分大小写的(也就是说它会搜索searchstring, searchstring, searchstring等等)。
This will search for all files and directories with "searchstring" in the name, and -i means the search is not case sensitive (i.e. it will find searchstring, searchstring, searchstring, and so on).
如果该文件确实存在，那么您可以就其区分大小写的名称到底是什么进行很好的猜测。
If the file does exist, then you can have a pretty good guess as to what its case-sensitive name might be.
因此您必须经历为每个用户数据库激活不区分大小写查询的整个过程。
Therefore you must go through the entire process for enabling case-insensitive queries for every user database.
这篇文章描述了关于这个过程更详细的细节，同时还阐述了如何归还到默认的区分大小写的查询中来。
This article describes this process in more detail and also explains how to revert to the default case-sensitive queries.
要开始激活区分大小写查询程序的过程，首先要复审用户数据库的模式，并确定所有的多行文本域。
To begin the process of enabling case-insensitive queries, review the schema of the user database and identify all of the multiline text fields.
与区分大小写有关的一个问题是：如果设置不正确，您可能无法访问一些文件。
One problem with case sensitivity is that set incorrectly, you might not be able to access some files.
这表明索引应该是不区分大小写的。
以不区分大小写的方式搜索DB 2数据有多种方法，比如使用生成的列(请参见参考资料)。
There are several methods to search DB2 data in a case-insensitive manner such as the use of generated columns (see Resources).
当您设置mcauser属性的值时，应该将值包括在单引号中，以避免分布式平台上的区分大小写问题。
When you set a value for the MCAUSER attribute, enclose the value in single quotes to avoid issues with case sensitivity on distributed platforms.
通常，一个验证检查包括检查一个用户的完整dn，检查是否在LDAP服务器中是唯一的，以及检查是否是区分大小写的。
Typically, an authorization check involves checking the complete DN of a user, which is unique in the LDAP server and is case sensitive.
如上所述，可以编写一条重命名规则将区分大小写的文件名转换为小写文件名，这样可能会与以前已存在的唯一的文件名发生冲突。
It's possible, as shown above, to write a rename rule that converts case-sensitive files into lowercase file names, thereby causing clashes among previously unique file names.
在每个XML文件中，都能发现一个类似的区分大小写的目标语句，这个语句指定了内容属于解决方案信息项目导航中的哪个位置。
In each XML file, you'll find a similar case-sensitive target statement that specifies where the content belongs in the navigation of a solution information project.
在内部，DB 2以不区分大小写的方式处理用户ID和组名。
Internally, DB2 processes user ID and group names in a case-insensitive fashion.
然而，并不是所有的查询都需要是区分大小写的。
本节介绍的方法有一个潜在的缺点：整个数据库中所有表中的所有列中的所有数据都是不区分大小写的。
The potential drawback of the approach described in this section is that all the data in all the columns in all tables in the entire database are treated in a case-insensitive manner.
如果一个应用程序查询这些XML文档，寻找某一城市的客户，那么很可能需要不区分大小写的搜索。
An application that queries these XML documents to find customers with a specific city most likely requires case-insensitive search.
访问元素是区分大小写的。
要想创建对于所有字符串比较不区分大小写的数据库，需要使用排序规则UCA500R1，见清单4。
To create a database that is case-insensitive for all string comparisons, it is necessary to use the collation UCA500R1 as shown in Listing 4.
换句话说，在不区分大小写的数据库中，字符串比较的开销可能会略微增加。
In other words, string comparisons may be slightly more expensive in a case-insensitive database.
提示：相同的脚本可以同时为区分大小写的和不区分大小写的查询创建索引。
Tip: The same script creates indexes for both case-insensitive and case-sensitive queries.
为了查明区分大小写的和不区分大小写的数据库之间的性能差异，我们创建了一个常规数据库（区分大小写）和一个不区分大小写的数据库。
To check the performance difference between queries in case-sensitive and case-insensitive databases, we created a regular database (case sensitive) and a case-insensitive database.
参数名是不区分大小写的。
应用推荐