Video

Could you explain about Always on.. in and out , Failover cluster as well please.

Could you explain about Always on.. in and out , Failover cluster as well please.

What are wait types?

Very informative session

Thanks so much for the eye opener video. Indeed learn somethg new :)

first one will do full cluster scan not seek. but the second one will be seeking the SC value. first query will not let the index do the job automatically or based on its plan. the second one does.

Thank you sir

Both will use a clustered index scan only. In equal will go index scan Equal operators will use seek but volume is bit high thats the reason its choose scan rather than seek

You do know that it's possible to run that query and get and compare those stored plan and the current plan?

Both will be clustered index scan only

Awesome video Amit, I'm looking for this kind of video. What if there's no hint recommendation for index scan operation of problematic queries. What will you suggest.

Nicely explained. Thank you Amit

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 czcams.com/video/jN6n1IwJKeQ/video.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 😢