Post reply

sp_start_job - Don''t know how to explain this

  • August 20, 2007 at 2:00 pm

    #728117

    What I did was just simply add a second step, controlled by a pass parameter to delete the entire job.

    Looking at the syntax for sp_add_job I can see that. Let me go back to the drawing board.. Thanks Lynn.

    Kurt W. Zimmerman
    SR DBA
    Lefrak Organization
    New York, NY

    http://www.linkedin.com/in/kurtwzimmerman

  • August 20, 2007 at 2:18 pm

    #728121

    Thanks for the tip. My failure to observed that simple feature cause some additional programming.. I reworked the call and removed some superfluous code. Thanks again.

    Kurt W. Zimmerman
    SR DBA
    Lefrak Organization
    New York, NY

    http://www.linkedin.com/in/kurtwzimmerman

  • August 20, 2007 at 2:43 pm

    #728129

    Glad to help!  Would like to know if it helps with the other issue you mentioned about all the jobs ending at the same time.

  • August 22, 2007 at 7:27 am

    #728552

    One last followup... I went forward and modified my script to toggle the delete option on my temp jobs and it worked fine, without any contention or deadlocking. Again thanks to Lynn for the suggestion. The jobs drop off at the same time, which again, isn't a real problem as long as the work gets done.

    Kurt

    DBA

    RHWI

    Poughkeepsie, NY

    Kurt W. Zimmerman
    SR DBA
    Lefrak Organization
    New York, NY

    http://www.linkedin.com/in/kurtwzimmerman

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply