Skip to main content

How to do a Case-Sensitive SQL Server Query

When selecting data in SQL Server, the WHERE-clause has, in my experience, ignored the case and done a case-insensitive comparison. For example, my Individuals table may have a mix of upper and lower cases, depending on how people entered their names:

SELECT firstname, lastname 
FROM Individuals
WHERE lastname = 'Timmins'

 firstname lastname
--------- --------
Tammy TIMMINS
Tellie timmins
Tommy TimMinS
Tubby Timmins

My query selected all four people with the last name "Timmins" without caring if it was all capitals, all lower case, or a mixture. I rely on that behavior all the time.

But once in a while, we need to do a case-sensitive query. How can we, for example, find Tommy TimMinS and correct it to Tommy Timmins?


The secret is to alter the Collation. This is a setting at the database-level, that controls the sort order within Unicode data types, and within non-Unicode character data types. (see here for an introduction)

To see the current collation setting of your database, in SQL Server Management Studio, right-click on the database and select Properties. The Collation setting lives on the General page, under Maintenance. The one my current project uses is "SQL_Latin1_General_CP1_CI_AS". The "CI" setting indicates that, for this database, order is Case Insensitive.

You can change the Collation property here, but it is a database-level property and there may be very good business and technical reasons it has its current settings.

Fortunately, you can alter the collation just for your query. In this way, you can still do a case-sensitive query in a database whose collation is set to Case-Insensitive collation.

My query above can be modified to select only the entries with the last name "TimMinS" by changing the "CI" for Case-Insensitive to "CS" for Case-Sensitive:
SELECT firstname, lastname 
FROM Individuals
WHERE lastname COLLATE SQL_Latin1_General_CP1_CS_AS = 'TimMinS'

 firstname lastname
--------- --------
Tommy TimMinS

I can also use this COLLATE key word to tailor the update and correct this value:
UPDATE Individuals 
SET lastname = 'Timmins' 
WHERE lastname COLLATE Latin1_General_CS_AS = 'TimMinS'

 (1 row(s) affected)

Now Tommy's last name should be "Timmins" with that exact case, while the other variants remain untouched. Let's check that, re-running the original query above:
SELECT firstname, lastname 
FROM Individuals
WHERE lastname = 'Timmins'

 firstname lastname
--------- --------
Tammy TIMMINS
Tellie timmins
Tommy Timmins
Tubby Timmins

There are more options than the two Collation settings I have identified here. Check your SQL Server documentation to find the appropriate one.
Labels:

Popular posts from this blog

Git Reset in Eclipse

Using Git and the Eclipse IDE, you have a series of commits in your branch history, but need to back up to an earlier version. The Git Reset feature is a powerful tool with just a whiff of danger, and is accessible with just a couple clicks in Eclipse. In Eclipse, switch to the History view. In my example it shows a series of 3 changes, 3 separate committed versions of the Person file. After commit 6d5ef3e, the HEAD (shown), Index, and Working Directory all have the same version, Person 3.0.
Read more

Scala Collections: A Group of groupBy() Examples

Scala provides a rich Collections API. Let's look at the useful groupBy() function. What does groupBy() do? It takes a collection, assesses each item in that collection against a discriminator function, and returns a Map data structure. Each key in the returned map is a distinct result of the discriminator function, and the key's corresponding value is another collection which contains all elements of the original one that evaluate the same way against the discriminator function. So, for example, here is a collection of Strings: val sports = Seq ("baseball", "ice hockey", "football", "basketball", "110m hurdles", "field hockey") Running it through the Scala interpreter produces this output showing our value's definition: sports: Seq[String] = List(baseball, ice hockey, football, basketball, 110m hurdles, field hockey) We can group those sports names by, say, their first letter. To do so, we need a disc
Read more

Java 8: Rewrite For-loops using Stream API

Java 8 Tip: Anytime you write a Java For-loop, ask yourself if you can rewrite it with the Streams API. Now that I have moved to Java 8 in my work and home development, whenever I want to use a For-loop, I write it and then see if I can rewrite it using the Stream API. For example: I have an object called myThing, some Collection-like data structure which contains an arbitrary number of Fields. Something has happened, and I want to set all of the fields to some common state, in my case "Hidden"
Read more

How to do Git Rebase in Eclipse

This is an abbreviated version of a fuller post about Git Rebase in Eclipse. See the longer one here : One side-effect of merging Git branches is that it leaves a Merge commit. This can create a history view something like: The clutter of parallel lines shows the life spans of those local branches, and extra commits (nine in the above screen-shot, marked by the green arrows icon). Check out this extreme-case history:  http://agentdero.cachefly.net/unethicalblogger.com/images/branch_madness.jpeg Merge Commits show all the gory details of how the code base evolved. For some teams, that’s what they want or need, all the time. Others may find it unnecessarily long and cluttered. They prefer the history to tell the bigger story, and not dwell on tiny details like every trivial Merge-commit. Git Rebase offers us 2 benefits over Git Merge: First, Rebase allows us to clean up a set of local commits before pushing them to the shared, central repository. For this
Read more

Code Coverage in C#.NET Unit Tests - Setting up OpenCover

The purpose of this post is to be a brain-dump for how we set up and used OpenCover and ReportGenerator command-line tools for code coverage analysis and reporting in our projects. The documentation made some assumptions that took some digging to fully understand, so to save my (and maybe others') time and effort in the future, here are my notes. Our project, which I will call CEP for short, includes a handful of sub-projects within the same solution. They are a mix of Web APIs, ASP MVC applications and Class libraries. For Unit Tests, we chose to write them using the MSTest framework, along with the Moq mocking framework. As the various sub-projects evolved, we needed to know more about the coverage of our automated tests. What classes, methods and instructions had tests exercising them, and what ones did not? Code Coverage tools are conveniently built-in for Visual Studio 2017 Enterprise Edition, but not for our Professional Edition installations. Much less for any Commun
Read more