Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Long Running Jobs Expand / Collapse
Author
Message
Posted Friday, May 20, 2005 12:47 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, November 16, 2016 6:05 AM
Points: 145, Visits: 335
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/lPeysakhovich/longrunningjobs.asp


Post #184263
Posted Wednesday, May 25, 2005 10:57 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, January 28, 2016 7:59 PM
Points: 71, Visits: 251

Instead of using the command shell to see if the SQL Agent Service is running.  You could use the following command.

EXEC master..xp_servicecontrol QueryState, SQLServerAgent




Post #185185
Posted Wednesday, May 25, 2005 11:23 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, November 16, 2016 6:05 AM
Points: 145, Visits: 335

Thanks for the tip. But the stored procedure you pointed is undocumented. I am trying to use only documented procs to be able to use it between SQL Server versions. Even Microsoft very seldom changing undocumented stored procs it may happened. Check a good tip about undocumented stored procedures in the last SQL Server Magazine and changes that are done with some of them in sp4.




Post #185190
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse