Assume that you have Microsoft SQL Server 2017 or 2019 installed, and that it runs withdefault Cardinality Estimation (CE). You execute a query that has a filter predicate on column Col1. Querypredicates have intrinsic UPPER, LOWER, or RTRIM. Col1 has statistics to beused by the optimizer. In this scenario, you may observe inaccurate cardinalityestimates and that SQL Server uses an inefficient plan. The following are some queries that have predicates:
SELECT person_id FROM Person WHERE (emailLIKE UPPER(Nemail@example.com%'))
SELECT person_id FROM Person WHERE (email= UPPER(Nfirstname.lastname@example.org'))
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative updates for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: