7 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• AdminPriya Sinha (Project Manager, Red Gate Software) commented  ·  March 11, 2013 2:06 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Thanks for your feedback Allen.

  Regards,
  Priya

• Allen Dunn commented  ·  March 8, 2013 10:02 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  The Job Step Failure alert is essential as currently jobs where the "quit the job..." option is not enabled you can miss failures.
  I am aware thet the job history in SQL Server GUI does not show failed steps if the last step completes, but it would be ideal to not have to query all servers for failed steps when SQL Monitor could pick them up.

• AdminPriya Sinha (Project Manager, Red Gate Software) commented  ·  October 31, 2012 1:04 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Thanks all for your suggestions.

• Stephen commented  ·  September 20, 2012 10:23 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  The additional SSIS info would be VERY helpful, especially as the SSISDB query from SSMS is a SLUG and cumbersome and calls for a lot of clicking to drill down to the information - and I only have ONE PACKAGE in SQL2012 to monitor!

• Blaž Dakskobler commented  ·  September 19, 2012 2:30 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I forgot an important comment about job steps:

  At the moment there is no alert in case a job step fails, but it is NOT set to "quit the job reporting failure"... ie. one can have a multi-step job where the desired behavior is that the steps execute no matter what happened in previous steps. In case one of those steps fails, an alert would be beneficial or even crucial.

• Blaž Dakskobler commented  ·  June 23, 2012 10:15 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Hey. The thing I'm missing most is the error message for the failed step. It's the message you see in job history GUI in SSMS for a particular job step. Of course there's other stuff there as well (step number, duration...).
  For SQL 2012 job steps that run SSIS packets, one step further would be to include error messages from the SSISDB catalog, since all the error message on job step says is something like "go check SSISDB catalog for more details" :)
  Hope that helps.

• AdminAdam (User Experience Specialist, Red Gate Software) commented  ·  June 22, 2012 6:35 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Hi, thanks for this suggestion. We're looking into this and will get back to you soon. In the meantime, let us know if you have any further details regarding what you consider to be the relevant information in the steps.

  Thanks again