Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am scheduling a report using SQL Server Reporting Services Subscription option. Suppose my rdl file is corrupted or my stored procedure has got some problem. Then the report won’t generate in its next turn. What can I have to get the intimation that the report does not generated properly?

Can I configure to get a mail on report generation failure

share|improve this question

migrated from Feb 1 '12 at 14:07

This question came from our site for professional and enthusiast programmers.

SSRS report subscriptions generate job entries in SQL Agent. Find the corresponding agent job and set email alerts through it's properties for failure.

share|improve this answer

For what it's worth - while exploring my own similar question alert when any job in a job category fails, I uncovered that while it is true that SSRS report subscriptions generate job entries in SQL Agent, the failure of an SSRS report subscription does not fail the SQL job.

You can find the failure in ExecutionLogStorage.Status in theReportServer database.

share|improve this answer
That is interesting. Is that expected behavior or a bug? – jgardner04 May 23 '12 at 19:29
I'm not sure - in some ways it makes sense since the Agent did its job and it is usually some SSRS thing that is broken... – JHFB May 23 '12 at 19:40
Yeah, I see that point too. Just interesting. I would love to here the argument from both sides, purely for academic reasons. – jgardner04 May 23 '12 at 19:43

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.