Does SQL Server has any priority for where clause when use and?

Question

I have 2 columns: Name and Price.

Price is a computed column which call a function to calculate the price with some queries.

Now I want to know is there any difference between :

select * 
from myTable 
where name like 'j%' and Price > 1000

and

select * 
from myTable 
where Price > 1000 and name like 'j%'

I want to know if I use name like 'j%' at first does it have better performance because maybe sql server does not check the computed column at first for all records ?

Well, when you ran them both and looked at execution time, what did you find? — dfundako, Aug 22 '18 at 16:37
@dfundako, I have not many records now, just I want to know it for the future. — Sepehr Estaki, Aug 22 '18 at 16:39
Absolutely no difference at all. The query engine will evaluate those in whatever order it feels will provide the best option for retrieval. It doesn't matter the order of predicates nor the order of value in each predicate. — Sean Lange, Aug 22 '18 at 16:39
@SepehrEstaki Fill your table with a ton of dummy rows and run it? — dfundako, Aug 22 '18 at 16:41
Exactly and to add to what Sean Lange said, the indexes you create on the table will have more effect on performance when you have lots of data. — Danielle Paquette-Harvey, Aug 22 '18 at 16:41
@SeanLange Thank you, if you sure about it, just post it as an answer so I can check your answer as an answered. — Sepehr Estaki, Aug 22 '18 at 16:43

score 0 · Accepted Answer · answered Aug 22 '18 at 16:44

0

Absolutely no difference at all. The query engine will evaluate those in whatever order it feels will provide the best option for retrieval. It doesn't matter the order of predicates nor the order of values in each predicate.

answered Aug 22 '18 at 16:44

Sean Lange

33,028
3
25
40

Does SQL Server has any priority for where clause when use and?

1 Answers1