Comments
2 comments
-
Thanks for your post. SQL Backup relies on the SQL Server Agent to be running in order for a scheduled task to be run.
Unless you're using Task Scheduler and calling an executable from the command line, any sort of scheduled job running in SQL Server relies on the SQL Server Agent to be running.
I'd therefore take a closer look at the SQL Server Agent and see why that's stopping, as to the best of my knowledge it shouldn't just stop through inactivity.
Kind regards,
Peter -
I went into Services and looked at the properties of Server Agent. It was set to run under the Network Service user. I then looked at SQL Server and it was set to run under Local System Account. I then changed Server Agent to run under Local System Account and started it. It stayed running.
My scheduled backup completed successfully last night! Thanks for your help.
-Phil
Add comment
Please sign in to leave a comment.
Right above the Job it says "Your SQL Server Agent doesn't appear to be running". I've clicked the Start SQL Server Agent link and it never goes away. I've also tried going into services and starting the agent. It comes back and says it quit because no one was using it. Is the agent my problem?
How do I get this scheduled job to start when it's supposed to?