SQL Server Jobs issue

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » SQL Server Jobs issue

SQL Server Jobs issue

Rate Topic

Display Mode

Topic Options

Author

Message

mahesh.dasoni

Posted Tuesday, September 11, 2012 8:56 PM

SSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 7:41 AM
Points: 81, Visits: 859

We have faced a scenario in which jobs are scheduled to run on daily basis,but one day what happened that the job didnt run and we didnt get any alert and as we work in a financial firm for which data is quite essential we suffered a heavy loss due to that job not running.

Is there any way through which we can track that job didn't run due to any reason.As it is virtually not possible to go on each server and check each job has run or not for that particular day as there are many servers and lots of jobs in that.
Urgent help is required.

Post #1357770

SQLRNNR

Posted Tuesday, September 11, 2012 9:24 PM

SSCoach

Group: General Forum Members
Last Login: Yesterday @ 1:07 PM
Points: 18,733, Visits: 12,332

You can set an alert to text or email you.

You can also create a job that checks for any failed jobs and then emails job results to you.

Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server 2008

SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp

Post #1357773

MissTippsInOz

Posted Tuesday, September 11, 2012 10:35 PM

SSC Veteran

Group: General Forum Members
Last Login: Monday, April 29, 2013 10:39 PM
Points: 286, Visits: 519

mahesh.dasoni (9/11/2012)

When you say the job didn't run, do you mean it never executed, or that it failed? If it is the former I would also be concerned to find out why the job didn't run and treat the root cause.

In my environment I have a PS script that runs across my whole environment each morning picking up job failures by interrogating the sysjobhistory table on each server. It drops the results into a table on a management server and I have an SSRS report that I check each day.

Clare
_________________________________________________________________________________________________________________
Measure twice; cut once (and have a good saw)

Hey, just a thought.....did you check Books Online yet?

Post #1357778

mahesh.dasoni

Posted Tuesday, September 11, 2012 10:47 PM

SSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 7:41 AM
Points: 81, Visits: 859

We have alert set virtually for everything but that day it didn't run due to sql server agent issue.

The error we got on sql server agent log was :-
SQLServer Error: 848, SQL Network Interfaces: The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you.

Is there any way through which we can check that particular job in a schedule has not run.

Post #1357783

MissTippsInOz

Posted Tuesday, September 11, 2012 10:58 PM

SSC Veteran

Group: General Forum Members
Last Login: Monday, April 29, 2013 10:39 PM
Points: 286, Visits: 519

You can query the sysjobactivity table in msdb to get various information regarding execution dates and times. The trouble with a job that doesn't run is that you won't find a log anywhere of it actually failing to execute so you will need to infer this from the sysjobxxx tables.

And do investigate the error you posted up further.

Clare
_________________________________________________________________________________________________________________
Measure twice; cut once (and have a good saw)

Hey, just a thought.....did you check Books Online yet?

Post #1357785

mrrobsewell

Posted Friday, September 14, 2012 6:52 AM

Forum Newbie

Group: General Forum Members
Last Login: Yesterday @ 8:47 AM
Points: 3, Visits: 282

I have a PS script that interrogates JobServer.Jobs on all servers across my estate at 7am.
So when I come into work it has emailed me a single email for each server if jobs have failed with the server name and the name of the job that has failed.

The same PS script also fills an Excel sheet and colour codes the results RAG for Failed Unknown Success which I check every day

Post #1359241

opc.three

Posted Wednesday, September 19, 2012 3:04 PM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 5:29 AM
Points: 6,698, Visits: 11,728

mrrobsewell (9/14/2012)

Nice! Care to share? If you don't mind post the script to this thread or contribute to the site by clicking the Write For Us link on the left nav.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato

Believe you can and you're halfway there. --Theodore Roosevelt

Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein

The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein

1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy

Post #1361634

« Prev Topic | Next Topic »

Permissions