Пікірлер

• 
  @jayaprakasharjunanКүн бұрын

  Loved it❤ template, color coding.. Thanks!!

• 
  @tugaycalk55513 күн бұрын

  Have you disabled lock escalation. If not why lock escalation not occur to table level with so much key level locks?

• 
  @andreabruschetta87917 күн бұрын

  What about Window Functions?

• 
  8 күн бұрын

  1.270 approximately

• 
  @vklude12 күн бұрын

  Didnt expect such a huge difference

• 
  @agux3e13 күн бұрын

  Inequality operators force SQL Server to scan the index instead of seeking in it.

• 
  @Harsha_vardhan114 күн бұрын

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

• 
  @Harsha_vardhan114 күн бұрын

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

• 
  @JgNt398115 күн бұрын

  What are wait types?

• 
  @PradeepKumar-oj2zs16 күн бұрын

  Very informative session

• 
  @Meerahparbutteeah20 күн бұрын

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

• 
  @SadamKam21 күн бұрын

  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.

• 
  @mallikamaragani769121 күн бұрын

  Thank you sir

• 
  @harshareddykalki24 күн бұрын

  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

• 
  @waynehamberg924825 күн бұрын

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

• 
  @harshareddykalki26 күн бұрын

  Both will be clustered index scan only

• 
  @kundanivlogs27 күн бұрын

  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.

• 
  @AmitKumar-pl4qm27 күн бұрын

  Nicely explained. Thank you Amit

• 
  @goksoy130528 күн бұрын

  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.

• 
  @goksoy130528 күн бұрын

  what is the difference

• 
  @claudineialbuquerque4775Ай бұрын

  Very good

• 
  @arghasen6535Ай бұрын

  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 .

• 
  @ssrakeshsharmaАй бұрын

  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

• 
  @kingvinay1285Ай бұрын

  Very much helpful thanks

• 
  @benf101Ай бұрын

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

• 
  @blackisblack22Ай бұрын

  🙏🤫

• 
  @agnaldosalesasrs892Ай бұрын

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

• 
  @mocococo2877Ай бұрын

  At kzread.info/dash/bejne/nIJq0JOCp62xlbQ.html you say "... optimistic concurrency is good and it should be preferred over optimistic concurrency .... " Please, clarify that.

• 
  @HunaismpАй бұрын

  Ambigous column name

• 
  @steveearle9678Ай бұрын

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

• 
  @gentlesoulolayemi3566Ай бұрын

  Left outer join

• 
  @poojanpatel2437Ай бұрын

  Left outer.

• 
  @barrowmusicsАй бұрын

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

• 
  @goksoy1305Ай бұрын

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

• 
  @RahulSharma-vi3csАй бұрын

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

• 
  @NeerajPant-pp6qxАй бұрын

  Thanks for sharing that great knowledge!!!!

• 
  @pradeepdnmАй бұрын

  thanks for this video. learned new method in XEvents.

• 
  @francismanalonАй бұрын

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

• 
  @hutchm92Ай бұрын

  Thank you!

• 
  @ramkarthik7968Ай бұрын

  Video is not clear

• 
  @uday10000singh2 ай бұрын

  How we know which queries are using those resources.

• 
  @sansak90982 ай бұрын

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

• 
  @amigoscanariosdeclashofclan2 ай бұрын

  Nice , thanks

• 
  @pvksmaheeth88162 ай бұрын

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

• 
  @tvskumar19902 ай бұрын

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

• 
  @AliciaMarkoe2 ай бұрын

  Thank you 🦋

• 
  @SadamKam2 ай бұрын

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

• 
  @RahulSharma-vi3cs2 ай бұрын

  Memory history can be also seen in same manner ??

• 
  @architectingme2 ай бұрын

  Non sargable