Home/ Questions/Q 7408093
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T05:51:00+00:00

For a while I thought, in order for the WHERE criteria to be evaluated

  • 0

For a while I thought, in order for the WHERE criteria to be evaluated correctly, I need to account for case sensitivity. I would use UPPER() and LOWER() when case didn’t matter. However, I am finding the below queries produce the same result. 

SELECT * FROM ATable WHERE UPPER(part) = 'SOMEPARTNAME'
SELECT * FROM ATable WHERE part        = 'SOMEPARTNAME'
SELECT * FROM ATable WHERE part        = 'somepartname'

SQL Case Sensitive String Compare explains to use case-sensitive collations. Is this the only way to force case sensitivity? Also, if you had a case-insensitive collation when would UPPER() and LOWER() be necessary?

Thanks for help.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The common SQL Server default of a case-insensitive collation means that UPPER() and LOWER() are not required when comparing strings.

    In fact an expression such as 

    SELECT * FROM Table WHERE UPPER(part) = 'SOMEPARTNAME'

    is also non-sargable i.e won’t use available indexes, due to the function applied to the part column on the left hand side of the comparison.

    • 0