Using Triggers for auditing changes to sql jobs
Recently there was a job that was changed to stop at a step earlier than normal (presumably for testing). When it ran that night, it didn't run all the steps. This job has a lot of dependencies which needed to be re-run the next day and caused a bit of chaos for a few applications, data warehouse data, and reports.
In order to see who made the change, there would have to be some sort of auditing running prior to when the change happened. Auditing of sql jobs and more had already been identified as a project for our department, but hasn't been prioritized yet. This of course, doesn't help identify what happened for this specific time. :)
In the mean-time, management wants to be able to track these types of changes. Therefore, I started researching the multiple options and found some common solutions: