How To Troubleshoot a Slow Running Query in SQL Server Extended Events & Wait Stats (by Amit Bansal)
HTML-код
- Опубликовано: 8 сен 2024
- Looking for comprehensive, deep-dive training on SQL Server Performance Tuning? Explore SQLMaestros All-In-One Performance Tuning Bundle. Five courses at a highly discounted price. sqlmaestros.co...
The bundled content focuses on internals, troubleshooting, query tuning, performance optimization, tips, tricks, and loads of content from the real world.
If you are a fan of live classes, you can explore the SQL Server Performance Tuning Master Class. 40 hours of deep-dive LIVE training. Attend LIVE & get the class recordings for a lifetime. sqlmaestros.co...
Excellent instruction. Thank you.
So this was the best vedio I have seen so far in SQL Administration..hoping to learn much more
OK, we got to know which query is waiting. But the query which is waiting is not the real culprit. How to find the query which made that Select query to wait?
It is the transaction query within the update statement that block the server's ressources. Until it release the resources the sql select statement will wait for the end of the transaction statement :)
@@itintegration1734 And if it's was 100 transactions ? Which query is waiting ?
awesome. would like to see now, how will you going to optimize the query statement itself. thanks
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
Guys I have a question - In this case we all knew there was another update query running on another window and when we rollback that tran we could then see the logs of extended events
But what if some tran is in progress and executed by another user and we don't know who is running that tran and unless and until that tran is completed or rolled back we would not see any logs.
What to do in this scenario ? @SQLMaestros
Excellent Bansal
Awesome sir, Very helpful
I just learned a thing or two, thx
Hi Amit,
If we talk about the same in two sp's then after identifying the LCKMS lock on query. How would we able to know which stored procedure is blocking our query.
really helpful video sofar, if anyone would help me out to lear the SQL dba spacially, it would be appreciated.
Really very helpful and well explained
Thanks a lot for the help.
Excellent explaination
Thank You !!
if you have a database running in production, how would you know what session to filter on ?
Excellent, thank you so much!
Excellent Video !
Very good article
we mostly have slow running queries issues in prod..for which i dont have access. So do i need to check with DBA for this?
Brilliant content! Very helpful!
Good video.. helpful
very useful
Hi Amit, I have created 2 XEvents on my server to track any deadlocks or long running quires (Longer than 2 minutes), they worked very well but i had major performance degradation on the server knowing that i didnt pick any global events. I had to stop those events and the performance picked back to normal. Any clues on what has gone wrong? Im sure XEvents supposed to be much better and less consuming than profiler.
can we use DBCC OpenTran?
Easier to check blocking session in sysprocess
It was very complex
Very correct but incomplete. We know it's blocked, but we don't know who's blocking it.
everything is cool but wy are you wearing the headphones ??
Whats the solution?
Super like :)
Wondefull. Learn something
i am trying join in your website but i didn't find out math Captcha
Hi Bansal
i have installed SQL server 2012 Express ,and i created table with 5000,000 Records ,but its performance execution is too slow
what should i do with it?
many thanks for replay
ayub Karem
SQL Server Express Edition uses 1 processor and 1 GB RAM .
Create necessary indexes for Your table depends on needs (I don`t know what the phrase "performance execution is too slow" - may be it means only ""Select * from Table"..
Thanks for your efforts and knowledge sharing.. thanks
oh ... he's saying SPID!!! OK, I un-disliked this video... sorry, I've always heard ESS PEE EYE DEE, not "SPID"... cool cool!
Scott Hartman oh really
Excellent explaination
Thank You !!!