Case sensitivity in vendor databases

Vendor databases have different settings for case sensitivity. This setting must be consistent across databases if either of these conditions are true:

A database is moved from one vendor to a different vendor.

A Rational® ClearQuest® MultiSite environment uses multiple synchronized databases with different vendor databases.

Database vendor	Possible settings	Comments
Microsoft Access	Not case-sensitive	Microsoft Access databases are not case-sensitive.
IBM® DB2® and DB2 UDB components for Rational Products	Case-sensitive	Case sensitivity affects data only and not database object names.
Microsoft SQL Server	Not case-sensitive, Case-sensitive	Case sensitivity affects database object names and data. It can be set by using the installation time option or the database creation time option.
Oracle	Case-sensitive	The case sensitivity affects data only and not database object names.

Setting case controllability of queries with Oracle databases

With Rational ClearQuest, multiline text fields are stored in Oracle databases in the Character Large Object (CLOB) data type. One consequence of supporting the CLOB data type is that by default all queries on multiline text fields return case sensitive data. Rational ClearQuest allows administrators running Oracle databases to control whether multiline text queries return case sensitive or case insensitive data. To activate this feature you must enable the user database with a value that allows the indexing of multiline text fields and run two SQL scripts, setup_cq_ora_user_clob.sql and setup_cq_clob_index.sql. For more information, see http://www.ibm.com/developerworks/rational/library/07/0531_clearquest/.