Відео

The primary reason for the different execution plans is the nature of the operators in the WHERE clause. The NOT IN condition in Query 1 necessitates a scan to check each row, while the equality condition in Query 2 allows for a direct seek to the matching rows.

what is the difference

Very good

Q1 . Cluster Index scan will be used as "not in" clause exclude the values used from the all possible persontype values Q2. Index Seek will be used if table data are properly distributed across all the possible persontype else cluster Index scan will be used for huge number of rows .

Hi Amit, Thanks for this Video, Shared this Video with one of my customer. Unfortunately likes on this video are less then Kachha Badam Dance🙂 - What is going in this world

Very much helpful thanks

"AddStress.cmd". Sometimes I think someone is running that file in my life.

🙏🤫

There r many ways to fix that U can ancapsulating But the shortest way is changing the AND to Where

At ua-cam.com/video/jN6n1IwJKeQ/v-deo.html you say "... optimistic concurrency is good and it should be preferred over optimistic concurrency .... " Please, clarify that.

Ambigous column name

Because your city predicate is in your ON clause and Mumbai is in the left table

Left outer join

Left outer.

It sometimes depends on the size of the data you are actually working with.

thx ı knew row_number or group by but ı didnt know this method,so I learned a different perspective :D

Thank you so much for this video , btw I have asked that question 😊

Thanks for sharing that great knowledge!!!!

thanks for this video. learned new method in XEvents.

Hey man, big supporter here. Thanks for sharing this content!

Thank you!

Video is not clear

How we know which queries are using those resources.

i still didn't understand,how usage information have been reflected,can anybody help me with query which he used to monitor usage.

Nice , thanks

This is by far the best video on indexing, i would like to know how to clear fragmentation on indexes automatically. (Rebuild or ReOrganize)

How to improve performance of a view where only joins are used without any 'WHERE' available.

Thank you 🦋

using functions technically changing the way how indexes work on this column.

Memory history can be also seen in same manner ??

Non sargable

very helpful, like the way you speak...i was searching for update stats for very large table columns and how to manage tempdb growth...thnx anyways.

👍👍👍👍

Thanx a lot Sir

What is mean by System idel process?

Your videos are difficult to learn and digestive 😢

Thank you very much

in the predicate TerritoryID is the first column because its equality condition and SalesOrderID is the second for its inequality condition. It's the best combination for selectivity.

You present a problem (an important, common one), a series of possible answers and.. subscribe to premium content to get the answer. This was nothing more than an ad. Thumbs down.

Interesting information, I always keep my head burning on why SQL keeps raising its memory consumption. Earlier I thought it was some issue with my local system. Now I understood why. Thanks a lot.

Excelente!

Thanks brother

That's a good demo. So after capturing the wait type what next? Becos seeing the issue causing the slowness is good how to deal with it also matter. Thanks

calculation is new for me. Thanks Amit.

Loved this. It is amazing how the indexes work

Fantastic!

Great!

Since the first column in the index key defines the primary ordering of the data, a query filtering or sorting on the second column may not benefit from a clustered index seek because the index is primarily ordered by the first column. The query optimizer may choose alternative access methods, such as a full index scan or a table scan, depending on factors such as data distribution and cardinality.