Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

help to tighten use of  cmdshell  or sp_start_job Expand / Collapse
Author
Message
Posted Wednesday, September 26, 2007 9:31 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Sunday, April 12, 2015 11:39 PM
Points: 6,785, Visits: 8,674
Comments posted to this topic are about the item help to tighten use of  cmdshell  or sp_start_job

Johan


Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere

- How to post Performance Problems
- How to post data/code to get the best help


- How to prevent a sore throat after hours of presenting ppt ?


"press F1 for solution", "press shift+F1 for urgent solution"


Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me
Post #403093
Posted Thursday, April 9, 2015 12:19 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, April 17, 2015 8:34 AM
Points: 3, Visits: 97
@Johan, Very interesting approach! I am considering using it, but I have a question: When the error is raised, which account does it run under? Nevermind! Just realized that the job is run by the alert, so it is run by the account that runs sql agent. Sounds like the disable of the job is a fun way to annoy my production DBAs! :) j/k.
Post #1675891
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse