Remove Case Sensitive SQL

Hi
how can I remove sensitive case in oracle session?
Oracle 9i
Windows 2003
thanks

AHA!!!
What you mean is how can I write a query to return data regardless of the case of the data. Sure Burleson has a page showing exactly how to do this, available in 10g and above: [HTML-DB, Oracle and Case Insensitivity|http://www.dba-oracle.com/t_case_insensitive_indexes_searches.htm]
Note this requires setting NLS_COMP (for compares) and NLS_SORT (for sorts); I think this is what you are questioning.
Prior to 10g, we have to do this the hard way, by using the UPPER or LOWER row functions on the data stored in the database. Note however, regardless of setting these NLS parameters, what others were saying is completely correct, Oracle commands are completely case insensitive. Generally speaking, all data stored in the data dictionary is uppercase, but only when the DDL is executed without double quotes enclosing object names. You can therefore have a table name "Mixed_Case" by creating it enclosed in quotes, but that means you will forever after have to refer to it using double quotes.
Edited by: ArnoldH on Dec 17, 2008 8:56 AM

Similar Messages

Case sensitive sql - table and field names

I have a weird problem.
I have a client which works with MS SQL SERVER 2000.
database collation name is: Turkish_CI_AS
at the beginning I have this sql statement:
"select value from [OWNER].setting"
but because this table exists in database as "SETTING", I get java.sql.SQLException -
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'setting'.
while I change the sql statement to:
"select VALUE from [OWNER].SETTING"
it works ok.
I uses also other databases, but it works ok with small letters.
How can avoid this problem? should I change all the sql statements to
upper case?
I will appreciate any help.
Thanks.

I am not sure about case sensitivity of tables, but as a convention, I always use table names in UpperCase separated only by _.
I don't remember this to be a problem with Oracle or Sybase.
***Annie***

Removing Case-Sensitive HFS

Dear all,
I am using a MacBook Pro, and have been using this machine for so many months. When I started using it, I formatted it as Case-Sensitive HFS. However, by this time, Case-Sensitive is causing so many of my programs to not work correctly. So, I would like to remove it.
What would be the most effective way to reformat my MacBook Pro to use Case-Insensitive HFS, and putting all of my applications/data/preferences back on to it with out any hassles. I have an external Firewire HD. Is there a program that would automate this process for me? Or am I just so out of luck and have to go to the tedious backup and restore process.

Use the Restore option of Disk Utility to clone your system to the external drive. Format the external drive using Mac OS Extended (Journaled) and partition it using the GUID partition scheme. Then boot from the external drive and repartition and format the internal drive. Then using Restore clone back from the external drive to the internal drive.
Partition and Format a Non-startup Drive
1. Open Disk Utility in the Utilities folder.
2. After DU loads select your external hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Click on the Option button and check the option for the GUID partition scheme, then click OK. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process will take 30 minutes to an hour or more depending upon the drive size.
Clone Using Restore Option of Disk Utility
1. Open Disk Utility from the Utilities folder.
2. Select the startup or source volume from the left side list.
3. Click on the Restore tab in the DU main window.
4. Drag the startup or source volume to the Source entry field.
5. Select the backup or destination volume from the leftside list and drag it to the Destination entry field.
6. Check the box to Erase Destination. Skip this step if you've already formatted the drive.
7. Double-check you got it right, then click on the Restore button.

Enhacement for removing case sensitive of the short text entered in Me21n

Hi very one ,
i want to write a enhancement to remove the case sensitive of the short text entered in me21n transaction code for service Number . ie .. whether i enter the text in captain letter or small letters it should fetch the exact data accordingly to the short text entered ( the respective service number should be retrieved ) , i think there will be some function module that will remove this case sensitive thing . plz help me out
Regards
Syed Akbar

Thank you, Kappy, for your quick and helpful reply to my (admittedly) not very quick question!
It strikes me as odd that Apple would appear to make the use of both lower- and upper-case letters possible in the short user-name, leaving the possibility that upper-case letters might lead to some problems/conflicts down the line. It would be helpful if they'd provide some explanation about this. Anyway, as I said, I'm very far from being an expert in all this, and appreciate that people like yourself on these
forums are willing to provide helpful feedback.
Best regards,
Stephen

Removing case-sensitivity requirement on Mac OS X?

I found the statement
"You cannot install Adobe products on a volume that uses a case-sensitive file system, such as HSFX (HFS+) or UFS. This limitation applies to both the startup drive as well as the drive onto which the software is installed."
on the support site at http://helpx.adobe.com/creative-suite/kb/error-case-sensitive-drives-supported.html.
Why? Are you actively working on removing this limitation?
(I have other software I must use that has the opposite condition — it requires HSFX. I have submitted the reverse request to them.)
Thank you!

Hi Soren42,
Unfortunately Adobe products cannot be installed on a volume that uses a case-sensitive file system, such as HSFX (HFS+) or UFS. This is a software limitation and is as designed.
You can fill out the feature request form ( https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform ) to request new features or suggest modifications to existing features.
Regards,
Rave

How to convert case-sensitive to extended journal format

I have two apple computers (extended journal format) that have been backed up via a time capsule. I have just noticed that the TC is formatted as case-sensitive. I do not know why case-sensitive. In an effort to ensure consistency of file format then I seek to somehow remove case-sensitive formatting. I presume no/minimal underlying case-sensitivity issues within file names as source data is not formatted in case-sensitive manner.
I have tried SuperDuper to clone the TC to an external HDD but the application cloned the formatting in addition to the data.
I have attempted use of Disk Utility to copy content from source (TC) to destination (HDD) but this yielded error messages that noted different file format types.
It there a way to convert/remove case sensitive formatting from TC?
I appreciate that I could simply reformat TC to extended journal format but this would presumably erase all my backup data.
Any guidance most welcomed.

RossM wrote:
So I guess my choice is to "leave well alone" as Pondini suggests and accept the fact that cloning TC onto HDD has now formatted my new HDD as case-sensititive.
Actually, you may have two choices, depending on how you're going to be backing-up to the new HD:
Your best bet, by far, is to back up to it directly, rather than connecting it to the TC. That's much faster and more reliable. If so:
* Leave the TC backups alone. Reformat the HD as case-ignorant and let Time Machine start fresh on it. You can always see and restore from the old ones via the Browse... option, per Time Machine - Frequently Asked Question #17.
* Format the HD as case-sensitive and copy the backups from the TC to it. But don't copy the whole sparse bundle; copy the Backups.backupdb folder from the sparse bundle to the top level of the HD. (Sparse bundles are used only for network backups.) See #18 in the FAQ; you'll need the 4th procedure (copy network backups to be used locally.
But if you're going to connect the HD to the TC and back up to it that way, it doesn't matter how you format the HD, since the backups must be in a sparse bundle, that has its own format. Two choices for that:
* Leave the TC backups alone. Connect the HD to the TC and select it as the TM destination, and Let Time Machine start fresh on it. You can always see and restore from the old ones via the Browse... option, as above.   (There is a way to speed up the first backup; see the blue box in #Q2 of Using Time Machine with a Time Capsule.)
* Copy ("Archive") the TC's internal disk to the external HD, per the green box in #Q6 of the same article. Then select the external as your Time Machine destination via Time Machine Preferences.
Is this simply deferring a problem issue to another time (aagh)? Or to somehow try and remove this inconsistency and remove case-sensitive formatting from all tech items, even if this might mean reformatting and losing old backup data?
No. There's not really a problem, unless you change the case of file/folder names and try to restore the old ones to the same place via the TM browser, per the link in my earlier post. That's the only possible downside.
Does Time Machine require case-sensitive formatting on its destination drive?
No. It's the default, but case-ignorant is fine, unless you ever want to add a case-sensitive volume. Then you're in a pickle.
Or does Time Capsule only function witih case-sensitive formatting?
No. The TC's actual disk is case-ignorant; it's only the Time Machine sparse bundle that's case-sensitive by default.
The benefit of case-sensitive formatting as Apple default seems rather unclear to me
It's the default only for Time Machine backups. Everything else defaults to case-ignorant.
The advantage is, once you've been backing-up your internal HD for weeks, months, or years, and want to add a case-sensitive external HD to be backed-up, you can.   If the backups are case-ignorant, you can't.

Setting case sensitivity for text searches

I am trying to figure out how to set case sensitivity for text searches for Oracle. I am using 8.1.7 and the documentation keeps referring me to the Basic_Lexer object. Does setting the mixed_case parameter to 'No' remove case sensitivity for the index or is there something else I need to do?

Do you recommend another field type that can be used that does not use case sensitivity?
Thank you

Column case sensitivity

Hi
Have connected to MS Access via HS but when run sql against external table is appears sql columns are converted to upper case prior to accessing the table
i.e. two columns on access table are
SpecimenID and LAB
Can select LAB from Linkdata@add_dr
select Lab from linkdata@add_dr
BUT
select SpecimenID from Linkdata@add_Dr fails with
ora-00904 "SPECIMENID" : invalid identifier
Is there a parameter which stop what seems to be converting column name into UPPERCASE
Using Access at the moment but target databases will be
case sensitive SQL Servers
Any thoughts would be appreciated
Thanks
Ian

Hi
that was easy - Works fine
have applied double quotes to all column names used in query
and now accessing external table without any problems
Curiously, have been using OCI from forms 4.5 to ODBC connect to same database without any problems !!
Hassle only occured when started using HS !
Thanks
Ian

Mac OS X 10.5: Can I change my system to be not case sensitive?

I was wondering if there was a way to remove case sensitive without reinstalling leopard on the computer

no. You need to erase the drive to change it from case sensitive to case insensitive.

Is a Full Text Index search case sensitive or not in SQL Server 2012?

I setup full text index on my contact table and am attempting to run a search on it using the following query:
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName, 'Test')
OR CONTAINS(C.LastName, 'Test')
The problem is it's clearly running a case sensitive search. I did a quick search to find out how to change it to be case in-sensitive and found two pages (both for SQL Server 2012) with conflicting answers:
1 - MSDN - "Query with Full-Text Search" - http://msdn.microsoft.com/en-us/library/ms142583(v=sql.110).aspx
Case sensitivity
Full-text search queries are case-insensitive. However, in Japanese, there are multiple phonetic orthographies in which the concept of orthographic normalization is akin to case insensitivity (for example, kana = insensitivity). This type of orthographic normalization
is not supported.
1 - TechNet - "Full-Text Search (SQL Server)" - http://technet.microsoft.com/en-us/library/ms142571(v=sql.110).aspx
Full-text queries are
not case-sensitive. For example, searching for "Aluminum" or "aluminum" returns the same results.
Can someone please explain this? Is it possible to do it without it being case sensitive? If yes, how?
(Sorry, I couldn't make those links b/c TechNet hasn't verified my account)
Thank you for your time and help,
Hanan

Whats the collation setting for the columns? try using a case insensitive collation as below
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
OR CONTAINS(C.LastName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Jdbc bug in executeUpdate(sql, int[]) when table name is case-sensitive;

I have found a bug in oracle's jdbc (ojdbc6.jar), can someone tell me how to submit it so that it can be fixed?
The BUG: using executeUpdate(insert_sql_stmt, int[]) to retrieve the generatedKey generated by before-insert trigger using a sequence results in error when the tablename is case-sensitive (but OK if table name in uppercase).
Steps to reproduce:
1a. create table "mixCase" (f1 integer, f2 varchar2(20));
1b. create table upperCase (f1 integer, f2 varchar2(20));
2a. create sequence mixCase_seq start with 1;
2b. create sequence upperCase seq start with 1;
3a. create or replace trigger mixCase_trigger before insert on "mixCase"
bq. for each row \\ begin \\ select mixCase_seq.nextval into :new.f1 from dual; \\ end;
3b. create or replace trigger upperCase_trigger before insert on upperCase
bq. for each row \\ begin \\ select upperCase_seq.nextval into :new.f1 from dual; \\ end;
4a. String url = "jdbc:oracle:thin:@//localhost:1521/orcl";
bq. conn=DriverManager.getConnection(url,user,password); \\ Statement stmt = conn.createStatement (); \\ int rc=stmt.executeUpdate("insert into \"mixCase\"(f2) values('aa')",new int[]{1});
4b. String url = "jdbc:oracle:thin:@//localhost:1521/orcl";
bq. conn=DriverManager.getConnection(url,user,password); \\ Statement stmt = conn.createStatement (); \\ int rc=stmt.executeUpdate("insert into upperCase(f2) values('aa')",new int[]{1});
When you run 4a or 4b in a java jdbc program:
4b runs OK and rset=stmt.getGeneratedKeys() returns the correct f1 value of 1.
4a results in error:
bq. h6. java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist \\ + at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)+ \\ + at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)+ \\ + at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)+ \\ + at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)+ \\ + at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:406)+ \\ + ...+
+Notes:</</em>
# If Statement.RETURN_GENERATEDKEYS is used instead of "new int[]{1}" in 4b, there is no error but the rset=stmt.getGeneratedKeys() returned in a ROWID such as 'AAARUyAAEAAAAGQAAL', not what is expected. Other database's jdbc return the correct generated integer value.
# Same 4b error if new String[]{"f1"} is used as 2nd argument for executeUpdate.
# The only difference in 4a and 4b is that 4a has case-sensitive table name. All sequence names, trigger names, column names are implicitly deemed to be uppercase by oracle in both cases.
bq.
Edited by: user10343198 on Oct 2, 2008 5:50 PM
Edited by: user10343198 on Oct 2, 2008 6:34 PM

Please patch one fo your machines to 10.2.0.3 and then try and duplicate. You do not have to go through the complete registration of the XSD process thoguh you can check and see if the c based parser will validate on the command line using the
schema executible under your oracle_home bin directory.
schema 1.xml 1.xsd
for example
if it dupes in 10.2.0.3 open a TAR with support so that we may bug it.
regards
Coby

Case sensitive within character literals in SQL Server and Oracle

I am migrating SQL Server database to Oracle database by using Oracle Workbench.
SQL Server is not case sensitive, but Oracle PL/SQL is case sensitive within character literals. for example, if sort the following string ('UN','Win', 'iS' ,'Ne','zS'), SQL Server will get ('iS', 'Ne','UN','Win','zS') order, but Oracle PL/SQL will return ('Ne','UN','Win','iS','zS') order.
Anyone has idea how I can get same result as SQL Server without change PL/SQL code (I don't want to change "ORDER BY typename" to "ORDER BY UPPER(typename)" for every stored procedure).
Thanks

Jimmy,
alter session set NLS_SORT=West_European;
is the closest thing I know of, but UPPER() is the only sure way.
West_European sort order is AaBbCc ... 0123456789
usually sort order is 0123456789 ABC ... abc ...

How to select a case sensitive value in SQL with C#

Hello,
I have an application that at the begining a user will login with a user name and password which is stored in the database. The SQL statement is as follows:
"SELECT id_employee FROM employee WHERE employee_number='" + txtUserName.Text + "' AND passWord='" + txtPassword.Text + "'";
For testing purposes I have set the password to the word test. The problem is, if the user enters in TEST or TeSt or TESt it will grant them access. How do I set it to force the correct case?
I am using SQL 2005 for the database.
Thanks!
~zero

You can also set Collation while comparing strings:
"SELECT id_employee FROM employee WHERE employee_number='" + txtUserName.Text + "' COLLATE Latin1_General_CS_AS AND passWord='" + txtPassword.Text + "' COLLATE Latin1_General_CS_AS";
All comments about not doing this type of quering using command string, instead of command with parameters, they are apsolutely right.
Nevertheless i will have only username as a parameter in the command and password will be return value from procedure. I will check for equality of entered password and returned one from command in C# code, and C# is case sensitive. There is a good security model implemented for password in AdventureWorks sample database for SQL Server 2005, in table Person.Contact.
That model use two fields for password, PasswordHash and PasswordSalt. PasswordSalt is randomly generated hash when password is modified and with that salt, password string is encrypted, which produce PasswordHash. So when you want to authenticate a user, execute a command that will return a row(PasswordHash and PasswordSalt) for entered username, and in application you will encrypt entered username with PasswordSalt. If generated string is equal with the one returned PasswordHash, then you have a valid login. If nothing is returned from command or they are not equal, you have invalid login.

Why Java is case sensitive unlike SQL?

Is it a good concept to have a case sensitive lang. or not.
Like we have SQL which is not case sensitive....so which is better concept and why.

Sheetal_Singh wrote:
But there sho be some logic behind this that sun devp made it case sensitive......
It become difficult for user to made code because we have to remember d case as well.
SQL cm afetr Java n it is not case sensitive,So microsoft must hav thought smthing that they made a case insensitive lang.Yes, you're absolutely right: when Microsoft set out to write SQL, they learned from Java's mistake and made it case-insensitive. Moving forward, Google is building on their experience to create an even more powerful language called "BASIC" that's not only case-insensitive, it has line numbers embedded right in the code!

Case sensitive issue CF7 & SQL 2005

I had to rebuild a database from a backup recently. Now I am having a case sensitive issue in my queries that I did not have before.
The following use to work with Rockmart in lowercase even though Rockmart was in the table as all uppercase like so ROCKMART.
<cfquery name="updateAreas" datasource="mySource">
   UPDATE Property
   SET AR = 3610
   WHERE City = 'Rockmart'
</cfquery>
The above has stopped working now the query must specify ROCKMART because it is in the table in all upper case.
My database option is set to SQL_Latin1_General_CP1_CI_AS
Any ideas.
Many thanks for you help.
Brian

A collation can be specified at the server, database, and column level in SQL server. The column collation will take precedence over the database collation. Check that the collation for the column is case-insensitive. You can use the query below to get the column's collation.
SELECT COLUMN_NAME, COLLATION_NAME
FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = 'Property'
    AND COLUMN_NAME = 'City'
You can get info on the collations supported by SQL Server at:
http://msdn.microsoft.com/en-us/library/ms144250%28SQL.90%29.aspx
You can change a column's collation if you need to, but you should be sure that this will not affect any other applications which query the same data. Another option is to specify the desired collation in your query as suggested by glynjackson.
http://msdn.microsoft.com/en-us/library/ms190920%28SQL.90%29.aspx

Remove Case Sensitive SQL

Similar Messages

Maybe you are looking for