How could capture a stop in SQLAgent regardless of why it stopped?

  • Hi forum.

    Please require an orientation with respect to the next subject.

    I entrusted the task of generating a procedure where they need to capture the exact moment when there is a stop in SQLAgent regardless of who did it or what it was that produced it. Frankly, I do not see where to begin to develop it. Could help a colleague to give any guidance on this.

    I hope Indeed understand me. Thank you all for your guidance and direction.

    Greetings,

    Jose Redondo

  • Would the agent always be started after it is stopped or not necessarily?

    There is a way to record when it starts, but skeptical that there is a way to record exactly when it actually stopped using SQL Server itself ... if you have outside application, it should be possible to monitor a stop ...

  • Getting the exact moment could be pretty tricky. There are clearly scripting methods to "query" windows services, which SQL Agent is, but even the best of monitoring apps do that on a "polling" basis from what I understand.

    You could also write a "log" scraper utility to scrape either the SQL Server Log file or the Windows application log file but again that would have to be done on a timed basis, i.e. every 5 seconds. I have no idea what the overhead would be on something like that.

    ....anyone else have any ideas?

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

Viewing 3 posts - 1 through 2 (of 2 total)

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