>>>>>This, that even the column names have to be matching in case, concerns me. I can deal with the values to be compared (by using UPPER()) but making sure that column names in my code match the names in tables will be a challenge.
>>>>>I hope more SQL Servers do not have case sensitive set ON.
>>>>>
>>>>
>>>>It is quite rare to have Case Sensitive installation of SQL Server. Usually if the SQL Server was installed with the wrong collation, the best course of action is to re-install the SQL Server.
>>>
>>>And then design your app to completely ignore case. If you are searching text, use case insensitive collation or UPPER() or LOWER() to make sure of it.
>>Using UPPER or LOWER function will not allow SQL Server to utilize indexes and will result in a table scan.
>
>Interesting point. Can you include UPPER or LOWER into the SQL Server index expression (so that index would be used0?

No. You can create a calculated field and index on that field. Indexes in SQL Server do not allow functions on the fields.