If you have a logging system, then you can easily check which jobs are running and which failed due to what, in the logs. There are a lot of good articles and tips, that can help you understand how to fix the jobs based on the logging data. If you have no logs, then it will be more difficult to understand what is going wrong and where. Also the following threads show you with a good way to get the failed SQL jobs, [sql server - What is the Query to display the failed sql jobs - Database Administrators Stack Exchange](http://dba.stackexchange.com/questions/88810/what-is-the-query-to-display-the-failed-sql-jobs), [How to obtain failed jobs from sql server agent through script? - Stack Overflow](http://stackoverflow.com/questions/10577676/how-to-obtain-failed-jobs-from-sql-server-agent-through-script) [Semi-Advanced Logging Options for SQL Server Agent Jobs | Practical SQL Server](http://sqlmag.com/blog/semi-advanced-logging-options-sql-server-agent-jobs) [sql server - Get detailed output of SQL Agent job - Database Administrators Stack Exchange](http://dba.stackexchange.com/questions/95333/get-detailed-output-of-sql-agent-job) [SQL Server Agent Error Log | Microsoft Docs](https://docs.microsoft.com/en-us/sql/ssms/agent/sql-server-agent-error-log) [How to debug jobs?](https://www.sqlservercentral.com/Forums/Topic1094893-391-1.aspx) Or even better would be to simply use the SQL Server Agent Jobs. The following will help on this, [How to: Create a SQL Server Agent Job (Transact-SQL)](https://technet.microsoft.com/en-us/library/ms181153(v=sql.105).aspx) [Create a Job | Microsoft Docs](https://docs.microsoft.com/en-us/sql/ssms/agent/create-a-job)
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~