we are using both DB2 and Oracle (db2 main) at our company.
My aim is to have some data (given contact names) to be shown on the screen ordered by the names BUT case insensitive. It is currently case sensitive and returns the contact names like; Bob, Caren, Don, ben, cameron, damien ..... whereas I want to have them like, Ben, Bob, cameron, Caren, damien, Don....
I did some research and found out the following which is a database level change offered since db2 9.5:
CREATE DATABASE testdb
USING CODESET UTF-8 TERRITORY US
COLLATE USING UCA500R1_LEN_S2
Now I still not too sure how it will affect all the platform.
I can not think of any risk regarding other db tables other than something as an example, contact_table which will work fine.
I just need to get some feedback on how risky can this change be.
Have you had any experience dealing with some problems after this change?
Can it be risky in any way?
Is there any other solution on this (except using UCASE or LCASE cause I still want to show the result as they are on the screen and not all lower or upper case)?
and the last question, does Oracle support the same thing?
I'd appreciate your feedback and helps on this topic.
This topic has been locked.
1 reply Latest Post - 2011-12-02T16:48:18Z by SystemAdmin
Pinned topic pros, cons, risk or danger of 'Making DB2 Case-Insensitive'
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2011-12-02T16:48:18Z at 2011-12-02T16:48:18Z by SystemAdmin
SystemAdmin 110000D4XK1731 PostsACCEPTED ANSWER
Re: pros, cons, risk or danger of 'Making DB2 Case-Insensitive'2011-12-02T16:48:18Z in response to comerunI am sure you got this figured out already, but I had a question. When you are pulling the data from the database is the name broken out? Another words will you have more than one part of the name in the column?
FIRST_NM LAST_NM MIDDLE_NM
BOB SMITH JOE
Or is it
BOB JOE SMITH