Hi guys, I need your help on this. I have an SQL Server that I use for reporting. Every morning at 4:45am, I have a job that loads data from my LIVE ERP system into my SQL Server. For a few months, the same jobs starts at around 11pm. I checked all my SQL Server instances and found no jobs or schedule like this. I also looked into a few system tables, but cannot find the source of this. I really need to be able to stop this job as it is taking resources and logs space for nothing. Can you please help me troubleshoot this so I can find where it is coming from ? Thanks PS : no idea of when it exactly started and what happened for this to happen BR Marc
It sounds like something other than the schedule is running the job, most likely using msdb.dbo.sp_start_job. It must be using either the job_name or job_id to start the job. If you change both of those it will stop. Here's what I would do: 1. Script the job. (Right click, Script As Create to New Window). 2. Save the script. 3. Comment out the contents of the job so it doesn't do anything if called. 4. Change the name of the job in the script (@job_name parameter of sp_add_job near the top of the script). 5. Run the script. 6. Test the new job. 7. If all looks well, delete the original job. I'd be surprised if this mystery thing can run the job after that. I would also review security. Which accounts have permissions to run jobs? Should they have those permissions?