Skip to main content

SQL Server–Does a ‘LIKE’ query benefits from having an index?

Last week I was interviewing a possible new colleague for our team. During the conversation we were talking about database optimization techniques and of course indexing was one of the items on the list. While discussing this topic, the candidate made the following statement:

An index doesn’t help when using a LIKE statement in your query.

This was not in line with my idea. But he was so convinced that I decided to doublecheck. Hence this blog post…

Does a ‘LIKE’ query benefits from having an index?

Short answer: YES!

The somewhat longer answer: Yes, a LIKE statement can benefit from an index in SQL Server, but its effectiveness depends on how the LIKE pattern is constructed.

Let’s explain this with a small example.

We created a Products table and an index on the ProductName column.

Let’s now try multiple LIKE statement variations:

Suffix Wildcard (Efficient Index Usage)

This query will benefit from the index because the wildcard is at the end:

Prefix Wildcard (Inefficient Index Usage)

This query will not benefit effectively from the index because the wildcard is at the beginning:

SQL Server has to scan all rows to find any products that end with "Pro".

Infix Wildcard (Partial Index Usage)

This query may partially benefit from the index depending on the database engine's optimization:

SQL Server can use the index to find rows starting with "Lap" but needs to scan those rows to find the ones that also match "op" at the end.

No Wildcard (Full Index Usage)

This query will fully benefit from the index as it effectively performs an equality check:

SQL Server uses the index just like it would for a direct equality (=) condition.

More information

https://use-the-index-luke.com/sql/where-clause/searching-for-ranges/like-performance-tuning

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...