|
|
|
Right there with Babe
      
Group: General Forum Members
Last Login: Thursday, February 14, 2013 12:01 PM
Points: 743,
Visits: 900
|
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: 2 days ago @ 5:08 AM
Points: 13,
Visits: 137
|
|
timothyawiseman (5/8/2008) Comments posted to this topic are about the item ...edited from article... Both sp_who and sp_who2 with its added columns can be tremendously valuable in scripts and programs, but for use on an ad hoc basis it is often more convenient to invoke the Activity Monitor GUI. ...edited from article...
Are you kidding me? If something is hanging up the server, the GUI will take minutes or longer to show you what's happening. Using sp_who2 is generally pretty fast even if the server is getting creamed by something.
I have a custom sp_who3 script which simply modifies the sp_who2 script to only show active processes. That way you can quickly see the active processes when something is slowing the server.
I find the GUI to be worthless.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, April 22, 2010 8:40 AM
Points: 6,
Visits: 13
|
|
| I would use Powershell for the first one and maybe write my own SP for the second. It takes me back to my unix days when wee had a whole list of shell scripts that we laid over the OS.
|
|
|
|
|
Right there with Babe
      
Group: General Forum Members
Last Login: Thursday, February 14, 2013 12:01 PM
Points: 743,
Visits: 900
|
|
rnjohnson10 (5/8/2008) Are you kidding me? If something is hanging up the server, the GUI will take minutes or longer to show you what's happening. Using sp_who2 is generally pretty fast even if the server is getting creamed by something.
....
You have a good point. Sp_who and sp_who2 will always be faster than the gui and that is particularly true if something is causing a general slow down.
With that said, I personally find the gui is often more convenient and more user friendly when looking for a specific block rather than a general slowdown. At least for me, both the procedures and the gui have their place depending on the situation.
--- Timothy A Wiseman SQL Blog: http://timothyawiseman.wordpress.com/
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Wednesday, May 21, 2008 11:38 PM
Points: 10,
Visits: 18
|
|
| All extended stored procedures mentioned in the article are well known to most of the people working with SQL Server for some years. They have been discussed many times in SQL server books and on popular SQL Server websites. Google search on "undocumented sql server stored procedures" returned 89,000 web pages. xp_FileExists for example is discussed at sqlservercentral, developersdex, databasejournal, sqlteam, dbforums, etc. The article lacks novelty but may be useful for some community members. That's why I rated it as 3-star.
|
|
|
|
|
UDP Broadcaster
      
Group: General Forum Members
Last Login: Wednesday, January 02, 2013 12:15 PM
Points: 1,443,
Visits: 711
|
|
| Nice work! Pretty comprehensive list, I've used most of these xp's in the past.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 12:29 PM
Points: 182,
Visits: 952
|
|
Nice list of stored procedures. You pointed out a few I was unaware of.
Thanks for sharing the info
David Bird
My PC Quick Reference Guide
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Wednesday, May 01, 2013 7:27 AM
Points: 903,
Visits: 8,640
|
|
Several of the examples were unreadable, displaying only a horizontal scroll bar. What might have been the example code was in a window which appeared to be 1 or 2 pixels tall.
Steve Eckhart
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 2:45 PM
Points: 209,
Visits: 324
|
|
Here's a caveat you can add to running sp_who2 to get just the running processes.
exec sp_who2 active
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Tuesday, August 09, 2011 1:09 PM
Points: 28,
Visits: 48
|
|
Steve Eckhart (5/9/2008) Several of the examples were unreadable, displaying only a horizontal scroll bar. What might have been the example code was in a window which appeared to be 1 or 2 pixels tall.
I was able to work around this glitch by printing the article to PDF. The code listings are printed inline with the article.
I agree with Steve that this UI bug should be fixed.
|
|
|
|