check out SQL job deleted

dear all,

right now we suspected that some SQL jobs has been deleted without our inspection, anyway to check what job has been delete during the last 3 months?
LVL 1
marrowyungSenior Technical architecture (Data)Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

slubekCommented:
Have you tried
select * from msdb.dbo.sysjobhistory

Open in new window

or
select * from msdb.dbo.sysjobactivity

Open in new window

?
1
Vitor MontalvãoMSSQL Senior EngineerCommented:
You need to have an old backup of MSDB database, then restore it with another name and check in sysjobs table if the jobs existed in that time are the same that you has now:
SELECT *
FROM sysjobs
ORDER BY name

Open in new window

0
marrowyungSenior Technical architecture (Data)Author Commented:
Vitor,

we can only do that by that method ?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Vitor MontalvãoMSSQL Senior EngineerCommented:
You can try slubek's solution but if don't works then only with an old backup you'll know which jobs were deleted.
0
marrowyungSenior Technical architecture (Data)Author Commented:
slubek,

both query seems the same, and it just has the job_id and instance_id, hard to tell which is which, right?
0
marrowyungSenior Technical architecture (Data)Author Commented:
Vitor,

yeah, the restore of MSDB is the last sort, but it didn't say who delete that, right?
0
marrowyungSenior Technical architecture (Data)Author Commented:
or the executing user in the message field is the only place to check who run that and who is deleteing that ?
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Unfortunaly won't say who deleted it. Will only prove that the job existed before.
0
marrowyungSenior Technical architecture (Data)Author Commented:
ok. OWOWOO. so from your point of view, no way to find it out anyway ?
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
You could have a chance to know it but then msdb need to be in full recovery model and you need to have the transaction log backups from that database. With that you'll need a log reader (usually a 3rd party software) that will be able to read a transaction log and then you'll found who and when deleted the job.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
marrowyungSenior Technical architecture (Data)Author Commented:
"With that you'll need a log reader (usually a 3rd party software) that will be able to read a transaction log and then you'll found who and when deleted the job. "

Apex Log for example ? you are trying to see what is inside that transcation log of MSDB ?
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Yes. If you have Apex log then you can give a try on it.
0
Mark WillsTopic AdvisorCommented:
Ouch...

By default MSDB uses simple recovery. So, unless you can interrogate MSDB itself, then it is going to be very difficult to find out "who" deleted the job.

Have you changed MSDB log to be full recovery ?

You might be able to find out the last time a job was executed, and then try to pinpoint activity during that time frame to see who was active at the time, but I think you will be out of luck.

Sorry about the bad news...

I will do a few searches on information and books that I have access to and see if there is any other glimmer of hope.

One thought to help pinpoint is querying the sysjobsteps
0
marrowyungSenior Technical architecture (Data)Author Commented:
Mark,

good to see you here again !

"
 Have you changed MSDB log to be full recovery ?"
no. so this mean it is a must ?


one question, anyone know if Apex Log tools can open the MSDB log when MS SQL is operating?

"EXECUTE msdb.dbo.sp_sqlagent_log_jobhistory "

this one need a @job_id

EXECUTE msdb.dbo.sp_sqlagent_log_jobhistory @job_id = 'D64C99DF-2A19-402C-A404-C4D768704E8E';

prompts an error:

Msg 201, Level 16, State 4, Procedure sp_sqlagent_log_jobhistory, Line 0
Procedure or function 'sp_sqlagent_log_jobhistory' expects parameter '@step_id', which was not supplied.

"is going to be very difficult to find out "who" deleted the job."

so can only from the  MSDB log file anyway, right ?
0
Mark WillsTopic AdvisorCommented:
Have  a read of : http://blogs.msdn.com/b/poojakamath/archive/2014/02/18/the-job-history-of-all-sql-server-scheduled-jobs-are-getting-deleted-automatically-on-a-daily-basis.aspx  (bit after the event, but could help if a recurring problem), also might be worth searching for : sp_delete_job
0
Mark WillsTopic AdvisorCommented:
If you are trying to find out who deleted a job by inspecting the log files, then yes, the log file would need to be as a result of having Full Recovery mode set on your MSDB (which is auto reset to simple everytime you run setup).

(BTW: I was in the middle of editing my post as you were reading it. Should have been querying sysjob... as per what can now be seen in my previous entry don't worry about that execute unless you know all the params)
0
marrowyungSenior Technical architecture (Data)Author Commented:
Mark,

you mean you write this post:

http://blogs.msdn.com/b/poojakamath/archive/2014/02/18/the-job-history-of-all-sql-server-scheduled-jobs-are-getting-deleted-automatically-on-a-daily-basis.aspx 

?

so as long as my MSDB is not in full recovery mode then nothing can be done. so this is it.
0
Mark WillsTopic AdvisorCommented:
No, I meant the earlier post. I realised that you need a LOT of detail to use that stored procedure to get history. Not that it would tell you who deleted, but would give you a timeline - but then (as others have said) there are system views/tables that can help identify a timeline, so changed my post from using the stored procedure to using the sysjob* views.

Sorry about that confusion.

To see deleted jobs, then you need the log file. For that log file to be useful, the DB needs to have been in full recovery mode.

Even then, you would need the timeline and tools to review the log file. Even then, the log may very well show a generic user or a process such as evidenced in the above link.

So, my initial response of "Ouch" is very much the case. I strongly believe (having been there before) that nothing can be done.

 Sometimes "it can't be done" is the correct answer, as much as we may wish it to be otherwise.

Moving forward, because jobs are removed using the stored procedure SP_DELETE_JOB you can create a SERVER audit to monitor that : http://blogs.msdn.com/b/sqlagent/archive/2011/02/21/auditing-sql-agent-job-creation-and-deletion.aspx

Or, if scheduling user generated tsql procedures, you can track modifications to those procedures using DDL triggers : http://technet.microsoft.com/en-us/library/ms186406.aspx  (I think we have discussed DDL triggers before)
0
marrowyungSenior Technical architecture (Data)Author Commented:
"Sometimes "it can't be done" is the correct answer, as much as we may wish it to be otherwise."

MS DBA exam like this !

"Or, if scheduling user generated tsql procedures, you can track modifications to those procedures using DDL triggers : http://technet.microsoft.com/en-us/library/ms186406.aspx  (I think we have discussed DDL triggers before) "

yes, but if someone use a system account to create that procedure, we can't do anything anyway, right?
0
marrowyungSenior Technical architecture (Data)Author Commented:
Dear both,

please help to answer this is you can:

http://www.experts-exchange.com/Database/MySQL/Q_28570501.html
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.