2. Some applications are case-sensitive, so be careful!
一些应用程序是区分大小写的，所以要小心！
来自互联网
3. The case-sensitive name of the schema to be backed up.
要备份的模式的大小写敏感名。
来自互联网
4. The password of the hub database user (case-sensitive).
hub数据库用户的密码(区分大小写)。
来自互联网
5. Both the attribute name and item type name are case-sensitive.
属性名和条目类型名称都是区分大小写的。
来自互联网
6. All USES of the name must match and the name is case-sensitive.
对名称的全部使用都必须匹配并且名称是区分大小写的。
来自互联网
7. Remember that when you enter your username, it is case-sensitive!
记住，当你输入用户名，它对大小写是敏感的。
来自互联网
8. The attribute name is case-sensitive, and its data type should be an integer.
属性名称有大小写的区别，且数据类型应为整数。
来自互联网
9. Repeat Step 5 for the request queue, specifying the following case-sensitive values.
为请求队列(request queue)重复步骤5，指定下列值(区分大小写)。
来自互联网
10. In the final step, indicate that the new index should support case-sensitive queries.
最后的步骤中，表明新的索引应该支持区分大小写查询程序。
来自互联网
11. Tip: The same script creates indexes for both case-insensitive and case-sensitive queries.
提示：相同的脚本可以同时为区分大小写的和不区分大小写的查询创建索引。
来自互联网
12. If the file does exist, then you can have a pretty good guess as to what its case-sensitive name might be.
如果该文件确实存在，那么您可以就其区分大小写的名称到底是什么进行很好的猜测。
来自互联网
13. When you create the index for each field, you can decide whether queries will be case-insensitive or case-sensitive.
当您为每个域创建索引时，您可以决定查询是否要支持区分大小写。
来自互联网
14. This article describes this process in more detail and also explains how to revert to the default case-sensitive queries.
这篇文章描述了关于这个过程更详细的细节，同时还阐述了如何归还到默认的区分大小写的查询中来。
来自互联网
15. For this example, the search string is also converted to lowercase, resulting in a search that is not case-sensitive.
在这个例子中，搜索字符串还被转换成小写字符，因此这个搜索不是大小写敏感的。
来自互联网
16. 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.
