Case Sensitivity
Oct 3, 2000Does anyone know if it is possible to disable case sensitivity without having to reinstall SQL Server?
View 2 RepliesDoes anyone know if it is possible to disable case sensitivity without having to reinstall SQL Server?
View 2 RepliesI am working on a C#/asp.net web application. The application has a text box that allows a user to enter a name. The name is then saved to the database.
Before the name is saved to the database, I need to be able to check if the name already exists in the database. The problem here is that what if the name is in the database as "JoE ScMedLap" and somoene enters the name as "Joe Schmedlap" which already exists in the database,but just differs in case.
In other words how do deal with case sensitiviy issues.
I am wondering if T SQL in SQL Server 2005 is case sensitive.
I running am running a query in a stored procedure whchi compares a passed in value with that in a field in the database, as such, is their a need to do thisSELECT * FROM table WHERE UPPER(column_name) = UPPER(@var) or will this return the same resultsSELECT * FROM table WHERE column_name = @var
When I do
select * from mytable where somecolumn='a'
I get rows for data with the value 'a' and rows for data with value 'A'
How to control cases sensitivity?
Thanks.
Hello !
I have two questions:
1) is it possible to make case sensetive researche in SQL-Server?
like : SELECT * FROM mytable WHERE myColumn = "This" [and not "this"]
2) is it possible to make case sensetive unique indexes? Allowing to add "This" and "this" in the same indexed column?
Thanks a lot for any feedback!
Regards,
Fabianus
my favorit hoster is ASPnix : www.aspnix.com !
Hi I have two questions about case sensitivity;
1. Do most people write their queries with UPPERCASE keywords or is that only for the textbooks. Personally I find it a hassle, My little finger aches because it is always on and off the SHIFT key
2. I noticed that when I did the following query
-----------------------------
use AdventureWorks
go
Select * employee
-----------------------------
I get an 'invalid object' message
But if I use;
--------------------------
use AdventureWorks
go
Select * Employee
--------------------
It works. SO obviously the query is case sensitive.
Did this use to be the case with SQL 2000. I don't seem to remember having to be careful about case.
THANKS
Is SQL server defaults to case insensitive? I am sure there are ways toinstall case sensitive SQL server instance but coming from Sybase(which is always case sensitive) case insensitivity is something new tome (it requires coding change etc).Besides, is there any option I can set to turn on case sensitivity or Iam stuck with it? (I can not reinstall SQL server).Thanks.
View 1 Replies View RelatedI scripted a function to a sql file, transferred the file to a different machine and when I run it it fails. It turns out that it thinks @result does not exist because I delcared @Result. Changing it to uppercase R resolves the problem. I usually keep my case sensitivity but missed this one. This is the first time I've ever seen sql care about the casing though! Is it a setting?
View 8 Replies View RelatedHello all,
I've come across a bit of an issue, I'm testing software delivered by another company that includes an SQL2005 database. I've rolled back their live database on my developer database, but my server has a binary collation set as default server collation.
Because of this (or so I think) all variable/table/etc names in any SQL code are case sensitive, even when called in the context of a database with a case insensitive collation. As an example, when I run the following code on my developer computer I get an error, on their live server I don't.DECLARE @number INT
SET @Number = 1
Because of this I am getting alot of errors from their code, since their entire application has differing capitalization usage from page to page. Is there any way around this or do I need to reinstall the SQL Server on my computer to set a different collation?
Any help would be appreciated, thanks in advance.
Hi,I believe my SQL server was configured as Case sensitivity. I have anumber of stored procedures which were moved from a non-Casesensitivity SQL server. Because of the Case sensitivity, I have to doa lot of editing in those stored procedures. Is there a quick way toavoid the editing?Something like ignoring the case in one statement?Thanks in advance, your advice will be greatly appreciated.
View 2 Replies View RelatedHi All,
How to remove case sensitity from database like table names,column names etc.
If we type either select * from AUTHORS" or "select * from authors" should result the same value.
Abdul
I require to change the case sensitivity of a server. If I run rebuildm (changing the sensitivity to the desired value) will that not mean that I won't be able to reattach the databases?
Can anyone advise please.
thanks
Derek
I have a case-insensitive sort order on my SQL7, NT4, SP1,2 installation. However, there are times when I want to do case-sensitive search ciriteria.
Is there something like the pseudo code:
SET SORT ORDER CASE-SENSITIVE ON
SELECT * FROM table WHERE name = 'Black'
SET SORT ORDER CASE-SENSITIVE OFF
..that doesn't return 'BLACK'
thanks in advance for your time
BL
Hi,
I use a SQL Server 2000.
Is there a chance to change the case sensitivity option for a running instance of sql server?
I know, during the install process, i can activate the case sensitivity. But can I change this option on an already installed server (to case sensitiv or back)?
Thanks
I have a SQL Server database hosted with a web hosting company. TheSQL Server was clearly set up to be case sensitive, however, I wantthis particular database to be case-insensitive.I have searched high and low, the best suggestion I can find is toreinstall SQL Server and select case-insensitive. But since this isthe web host's SQL, that isn't an option here.With default language I can use the sp_defaultlanguage to change toBritish settings (for example). Is there something similar I can useto make just this database case insensitive?--Popular uprising?http://www.blairfacedlies.org/statue.htmcaptain(underscore)flack(squirlything)hotmail(you know what)com
View 2 Replies View RelatedI have a query which filters records containing uppercase andLowercase i.e.Smith and SMITH, Henderson and HENDERSON etc.Is there a way that I can filter only those records that contain thefirst uppercase letter and the remaining lowercase letters for myquery i.e. Smith , HENDERSON etc.Thanks
View 6 Replies View RelatedHi All - I am using OpenXML to insert data into SQL Server 2005. All works okay except for the fact that in my XML I have an attribute tag and elements as follows.<Location> <Place City = "LA" State = "CA"> <Place city = "NY" State = "NY"> <Place City = "St. Louis" state = "MO"></Location> If you notice in the above code, the 2nd city NY has element tag "city" in lower case and others are "City" with a Upper Case "C" same for state in case of MO which is lower case and others are Upper Cases..Now I understand that XML is case sensitive. What should I do if I have XML files in the above format with inconsistent element tags? Because if I run the below code.. using OpenXML...Insert Into TableXSelect *FROM OPENXML (@DocHandle, '/Location/Place', 1) WITH (City varchar(255) '@City', State varchar(255) '@State') ox Then in the above scenario it won't insert values for city "NY" and state "MO" since both have lower case elements tags and in my OpenXML I have specified as @City and @State with Upper Case "C" and "S" respectively. Now in such a scenario what can one do? Any thoughts is to how I can also grab value for lower case "city" and "state" in the above XML. Any help would me much appreciated. Thanks a billion.Regards- web
View 2 Replies View Related
So I have been unfortunate enough to inherit a whole estate of sql servers running a collation of Latin1_General_BIN.
I have a batch of maintenance and monitoring scripts that I want to implement on these servers. However I seem to have problems compiling the stored procs as the case of the column names varies throughout the script and table definitions.
Ok I know I could recode them, but is there way to overide the case sensitivity in insert and update statements so they dont have to be recoded?
With Sql Server Management Studio, while creating/modifying a table I want to specify one of its columns to store values in lower case only. Can it be done through the designer or by some other means?
N.B.: Using SQL Server 2005.
Hi everybodyI'm a newbie to SQL-Server 2005 so please excuse me for my silly questionsRecently i wrote a simple web-Page in which i select data from a table and then bind them to a GridView on the formevery thing was simple as follows:
SqlConnection Con = new SqlConnection("Data Source=.;Initial Catalog=Test;Integrated Security=True"); Con.Open();
SqlDataAdapter da = new SqlDataAdapter("SELECT [ID], [Name], [Date] FROM [Table1] ORDER BY [Date]", Con); DataSet ds = new DataSet(); da.Fill(ds,"MyTable");
GridView1.DataSource = ds.Tables["MyTable"]; GridView1.DataBind();
But I have a question , when i change the [Table1] to [table1] (With lowercase T) , i receive the following errormessage:
Invalid object name 'table1'.
why is that? could anyone help me? even i tried to test this issue in [Microsoft Management Studio] and i got thesame result . realy what's the reason? before and with sql server 2000 i didn't have these issue.
Thanks in advance.Regards.
This is kind of a big generic question, if anyone could even just point me to an article or white paper on this it would be helpful, but I can't find an answer. I do work for a international company that currently does all in english, but is looking to support more languages.
What exactly do the Accent and Kanatype Sensitivity tags in RDL refer to, and how would/when should they be used?
Thanks for any help
Hi all,
I have a data mining model that has a binary dependent variable (let's say 'Yes' and 'No'). I noticed that the model is very sensitive to the distribution of the binary dependent variable. I could not come up with an explaination. I know the model is not over/under fits and multicollinearity is not an issue. And I have enough data size to train the model.
I would expect some sensitivity but not to this extend:
Yes % in training data
Yes % in the prediction results
with DT
with LR
with NN
30.0%
6.0%
11.0%
14.0%
35.0%
12.0%
15.0%
24.0%
37.5%
20.0%
23.0%
27.0%
40.0%
28.0%
33.0%
36.0%
50.0%
43.0%
52.0%
61.0%
DT - Decision Trees
LR - Logistic Regression
NN - Neural Networks
And to make things more interesting, although the precision (% of correct 'Yes's ), true positive ratio and false positive ratio is changing; the overall accuracy (and therefore the score in the mining accuracy chart) remains almost same.
If anyone has an idea it would be highly appreciated.
Thanks in advance, Afsin
How can I change my T-SQL text editor from text sensitive to text insensitive?
View 2 Replies View RelatedHello:
I have created an SQL server table in the past on a server that was all case sensative. Over time I found out that switching to a server that is not case sensative still caused my data to become case sensative. I read an article that said you should rebuild your master database then re-create your tables. So after rebuilding the master database, a basic restore would not be sufficient? I would have to go and manually re-create every single table again?
Any suggestions?
Can someone point me to a tutorial on how to search against a SQL Server 2000 using a case insensitive search when SQL Server 2000 is a case sensitive installation?
thanks in advance.
We need to install CI database on CS server, and there are some issueswith stored procedures.Database works and have CI collation (Polish_CI_AS). Server hascoresponding CS collation (Polish_CS_AS). Most queries and proceduresworks but some does not :-(We have table Customer which contains field CustomerID.Query "SELECT CUSTOMERID FROM CUSTOMER" works OK regardless ofcharacter case (we have table Customer not CUSTOMER)Following TSQL generate error message that must declare variable @id(in lowercase)DECLARE @ID INT (here @ID in uppercase)SELECT @id=CustomerID FROM Customer WHERE .... (here @id in lowercase)I know @ID is not equal to @id in CS, but database is CI and tablenames Customer and CUSTOMER both works. This does not work forvariables.I suppose it is tempdb collation problem (CS like a server collationis). I tried a property "Identifier Case Sensitivity" for myconnection, but it is read only and have value 8 (Mixed) by default -this is OK I think.DO I MISS SOMETHING ????
View 4 Replies View RelatedI am working in a SQL server database that is configured to be case-insensetive but I would like to override that for a specific query. How can I make my query case-sensitive with respect to comparison operations?
Jacob
I have column with value of all upper case, for example, FIELD SERVICE, is there anyway, I can convert into Field Service?
View 7 Replies View RelatedI am curious with using replication in sql server 2005 one way from db A (source) replicating to db B(destination) in which db A has a collation of CS and db B has a collation of CI. Will there be any problems with this scenario? Thanks in advance!
View 2 Replies View RelatedI have a view where I'm using a series of conditions within a CASE statement to determine a numeric shipment status for a given row. In addition, I need to bring back the corresponding status text for that shipment status code.
Previously, I had been duplicating the CASE logic for both columns, like so:
Code Block...beginning of SQL view...
shipment_status =
CASE
[logic for condition 1]
THEN 1
WHEN [logic for condition 2]
THEN 2
WHEN [logic for condition 3]
THEN 3
WHEN [logic for condition 4]
THEN 4
ELSE 0
END,
shipment_status_text =
CASE
[logic for condition 1]
THEN 'Condition 1 text'
WHEN [logic for condition 2]
THEN 'Condition 2 text'
WHEN [logic for condition 3]
THEN 'Condition 3 text'
WHEN [logic for condition 4]
THEN 'Condition 4 text'
ELSE 'Error'
END,
...remainder of SQL view...
This works, but the logic for each of the case conditions is rather long. I'd like to move away from this for easier code management, plus I imagine that this isn't the best performance-wise.
This is what I'd like to do:
Code Block
...beginning of SQL view...
shipment_status =
CASE
[logic for condition 1]
THEN 1
WHEN [logic for condition 2]
THEN 2
WHEN [logic for condition 3]
THEN 3
WHEN [logic for condition 4]
THEN 4
ELSE 0
END,
shipment_status_text =
CASE shipment_status
WHEN 1 THEN 'Condition 1 text'
WHEN 2 THEN 'Condition 2 text'
WHEN 3 THEN 'Condition 3 text'
WHEN 4 THEN 'Condition 4 text'
ELSE 'Error'
END,
...remainder of SQL view...
This runs as a query, however all of the rows now should "Error" as the value for shipment_status_text.
Is what I'm trying to do even currently possible in T-SQL? If not, do you have any other suggestions for how I can accomplish the same result?
Thanks,
Jason
Yesterday I received a response to my CI/CS Collation problem and therecommendation was to try and restore a CI Collation database to a CSCollation database. After creating a blank CS database a full restore(Force restore over existing database) does change the Collation toCI. I'm unsure as to how I can restore without changing theCollation. Any suggestions?
View 2 Replies View RelatedI just can't get the case to work for me in this view.
CASE WHEN Isnull(dbo.Payments.AmountPaid,'No') THEN 'No' WHEN dbo.Payments.AmountPaid >0 THEN 'Yes' END AS Payment_StatusThe error I get is:
An expression of non-boolean type specified in a context where a condition is expected, near 'THEN'.
ALTER VIEW [dbo].[AffiliationPayments]ASSELECT dbo.Affiliations.AffiliationType, dbo.Affiliations.AffiliationDescription, dbo.Affiliations.AffiliationEnd, dbo.Payments.PaymentDate, dbo.Payments.AmountPaid, dbo.Affiliations.Client_ID,CASE WHEN Isnull(dbo.Payments.AmountPaid,'No') THEN 'No' WHEN dbo.Payments.AmountPaid >0 THEN 'Yes' END AS Payment_StatusFROM dbo.Affiliations LEFT OUTER JOIN dbo.Payments ON dbo.Affiliations.Client_ID = dbo.Payments.Client_ID
I have a deadline that is set ahead of time and will not change. I need to insert this deadline for all new users, so I want to set in the DB and I have tried to insert the deadline into the db using a case(below)
Error -2147217900
Error -2147217900
Incorrect syntax near the keyword 'CASE'.
ALTER PROCEDURE prcStartWeeks @UserID VARCHAR(50) ASSET NOCOUNT ONDECLARE @Result INTDECLARE @ID INTDECLARE @Weeks INTDECLARE @DeadLine VARCHAR(8)SET @ID = 0SET @Weeks = 1SELECT @ID = ISNULL((SELECT peID from tblUserInfo where UserID = @UserID),0)IF @ID = 0 BEGIN SELECT @Result = -1 ENDELSE BEGIN WHILE @Weeks < 18 BEGIN CASE @Weeks WHEN '1' THEN @DeadLine = '5/9/2006' WHEN '2' THEN @DeadLine = '9/15/2006' WHEN '3' THEN @DeadLine = '9/22/2006' WHEN '4' THEN @DeadLine = '9/29/2006' WHEN '5' THEN @DeadLine = '10/6/2006' WHEN '6' THEN @DeadLine = '10/13/2006' WHEN '7' THEN @DeadLine = '10/20/2006' WHEN '8' THEN @DeadLine = '10/27/2006' WHEN '9' THEN @DeadLine = '11/3/2006' WHEN '10' THEN @DeadLine = '11/10/2006' WHEN '11' THEN @DeadLine = '11/17/2006' WHEN '12' THEN @DeadLine = '11/21/2006' WHEN '13' THEN @DeadLine = '11/28/2006' WHEN '14' THEN @DeadLine = '12/5/2006' WHEN '15' THEN @DeadLine = '12/12/2006' WHEN '16' THEN @DeadLine = '12/19/2006' WHEN '17' THEN @DeadLine = '12/28/2006' END INSERT INTO tblUserWeekly(PEID,WeekID,Points,DeadLine) VALUES(@ID,@Weeks,0,@DeadLine) SET @Weeks = @Weeks + 1 END SELECT @Result = 0 END