|
Comments
|
|
Good method ... put part 1 & 2 together to make 1 better
|
|
Joe Tigeleiro on
2/21/2009
very good series
|
|
|
awesome
|
|
Peter Voutov on
4/30/2009
I think it was great for a short video. I would have shown how to retrieve the stored procedure name along with the blocked/blocking statements within it. In the example, we knew which procedure the statements reside in, but in real life they might be in different procs.
|
|
|
I think Peter is right on. Knowing the SP would be of great help. This could easily have been down by also displaying the complete "text" column from the sys.dm_exec_sql_text DMV.
|
|
Steve Harris on
4/30/2009
confusing and hard to follow.
|
|
|
very nice tips!
|
|
|
excellant example
|
|
|
It would be nice to have a way to download your code.
|
|
|
oops, I just found the zip file. Nice video!
|
|
|
I used to use sp_who2 and dbcc inputbuffer(spid) to find the blocking process and its code,does sys.dm_exec_requests and
sys.dm_exec_sql_text have any advantages over the old ones?
|
|
|
but do you tune off the trace after you are done?
|
|
|
I'm sure there is an easier way to see what statements are blocking and blocked - isn't there something in SSMS to do this already?
|
|
|
excellent video, could do with a query to return the blocked and blocking statements as an alert of some kind?
|
|
|
Too advanced for me.
|
|
|
Good one,Jonathan
|
|
|
very heavy going and delivered very fast, but excellent content. It will probably take me another 2-3 hours to follow these example thru by myself to make sure I really understand everything.
|
|
|
When there are multipart video tutorials it would be nice if you put a link to the previous tutorial.
|
|
|
Very good but needs some more explanation, looks like some link is missing.
|
|
|
Very informative. I am learning quite a lot here.
|
|
|
very useful
|
|
|
Missing names of functions in the video
|