SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


usp_who5


usp_who5

Author
Message
Sean Smith (SSC)
Sean Smith (SSC)
Right there with Babe
Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)

Group: General Forum Members
Points: 715 Visits: 989
No problem. I seem to remember something about certain "date / time" columns in some of the system tables having ridiculous values (sometimes) for some reason which could be the issue (unfortunately I don't remember 100% what the details were behind that, could have been something I briefly scanned in an article on the net...). Let me know if it continues and you manage to track down the raw data value. With this I can write handling for it. Smile
Sean Smith (SSC)
Sean Smith (SSC)
Right there with Babe
Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)

Group: General Forum Members
Points: 715 Visits: 989
FYI: A few minor changes coming...

Minor Code Formatting Changes / Bug Fixes And Changes To Date Calculation Methods
jfogel
jfogel
SSChasing Mays
SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)

Group: General Forum Members
Points: 647 Visits: 1168
Very nice

Cheers
Sean Smith (SSC)
Sean Smith (SSC)
Right there with Babe
Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)

Group: General Forum Members
Points: 715 Visits: 989
Thank you! Smile
jfogel
jfogel
SSChasing Mays
SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)SSChasing Mays (647 reputation)

Group: General Forum Members
Points: 647 Visits: 1168
The more I look at it the more I like it. This thing really does have everything you need in one place. I tested it on 2005, 2008 and 2012 and found no issues. Great work and thanks for taking the time to put this together.

Cheers
Sean Smith (SSC)
Sean Smith (SSC)
Right there with Babe
Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)

Group: General Forum Members
Points: 715 Visits: 989
Thank you, again! I really tried to make it a "one-stop" stored proc. Smile
Sean Smith (SSC)
Sean Smith (SSC)
Right there with Babe
Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)

Group: General Forum Members
Points: 715 Visits: 989
For anyone interested, I just submitted a new version of the proc (still awaiting approval from SQL Server Central though...).

Additional output columns added:

Batch_Pct: Percentage of the batch which has been processed
Command_Pct: Percentage of work completed (applicable to a limited set of commands)
Command_Time_Left: Time left before the command completes (DAYS HH:MM:SS)
Command_Completion: Estimated completion time for the command
Deadlock_Priority: Deadlock priority of the session
Isolation_Level: Isolation level of the session
Last_Row_Count: Row count produced by the last statement executed in the batch
Lock_Details: Lock details of the session (in XML format)
Lock_Timeout_Seconds: Lock timeout of the session
Previous_Error: Previous error returned by the session

Hope everyone likes the updates.
Sean Smith (SSC)
Sean Smith (SSC)
Right there with Babe
Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)

Group: General Forum Members
Points: 715 Visits: 989
The new version's online. Smile
rfulbrig
rfulbrig
Grasshopper
Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)

Group: General Forum Members
Points: 11 Visits: 17
You have created a great script! The info is exactly what is needed to pinpoint blockages. The format of your select statement also makes it extremely easy to re-arrange the output columns to put the values most important to me up front.

I discovered that copy/paste from the web page converts periods to special characters in some places, but those were quickly cleaned up. You probably have no control over how the web page processes them during copy/paste anyway. Again, thanks for the great script!
Sean Smith (SSC)
Sean Smith (SSC)
Right there with Babe
Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)Right there with Babe (715 reputation)

Group: General Forum Members
Points: 715 Visits: 989
rfulbrig (11/3/2014)
You have created a great script! The info is exactly what is needed to pinpoint blockages. The format of your select statement also makes it extremely easy to re-arrange the output columns to put the values most important to me up front.

I discovered that copy/paste from the web page converts periods to special characters in some places, but those were quickly cleaned up. You probably have no control over how the web page processes them during copy/paste anyway. Again, thanks for the great script!


Thank you very much, I am so glad it helped you. Just curious, what web browser are you using to copy / paste the script?
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search