Post reply

Calendar report for SQL Agent Jobs - what GUI do you recommend?

  • August 19, 2021 at 10:14 pm

    #3921908

    Looking to create  a Calendar report for SQL Agent Jobs, to display the future (1 week, e.g.) and past (already run) jobs just like the calendar entries are shown on a regular calendar.

    I ve been predominantly DBA/DevOpser/DB Developer for a decade). Its been a while since VB6, first version of .NET, or ASP 2.. (my last GUI experience), so i am not sure what GUI to use for such project? SSRS Ok? Are there any issues why I may not want SSRS for that?

    it would always enable us at any given moment to know:

    this Friday at 3 p.m. such and such job(s) will be launched (that at previous run took 15 minutes.. (e.g.) ),

    and last Friday at the same time this and that job was run as well. And have a quick glance compare that way. It seems to be a useful report for anyone of us. And for the management , too.

    We are talking about several servers with 500 to 1000 jobs each.

    IF you are advising against SSRS then why?

    if SSRS then will using a Calendar control work?

    Thank you.

     

     

    Likes to play Chess

  • August 20, 2021 at 11:10 pm

    #3922286

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • August 21, 2021 at 3:53 pm

    #3922440

    You say you want it to be displayed "just like the calendar entries are shown on a regular calendar".  If you have 500 to 1000 jobs on a server lie you say you do and even just 10% run every day, I'm thinking that's pretty much doomed to failure because each day would contain 50 to 100 entries.  And you're saying you want such a calendar output for a week before and a week after?  I'm thinking that wouldn't actually be real useful.

    If you want to know what's going to be running (based on duration history) for a given time frame, go for that as table-like output.  I don't believe you need anything fancy for formatting for such inquiries either.  Why isn't the output in an SSMS session good enough instead of bothering your SSRS system with yet another report that takes too long to render and deliver?

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • August 22, 2021 at 3:58 am

    #3922518

    Thank you.

    I totally agree. There is a limit of how many jobs calendar can display.

    Is there any calendar control (existing control like for .Net) that would allow to click on an hour (say, 23:00 will be highlighted if there are jobs scheduled for that hour) and get a breakdown in a tabular report then?

    Likes to play Chess

  • August 22, 2021 at 4:41 am

    #3922524

    I'm going to have to defer to someone else on that question for details.  I stopped doing anything like that way back in 2003.  I do remember that there was a calendar control that would allow you to do that in old VB and see no reason why .Net or any other language capable of driving a GUI wouldn't have such a control.  As with all else, I suspect that Google would be your friend there.

    I can tell you that generating the report might produce a bigger report than you were expecting but it would be fairly easy to do in T-SQL.  Just remember the simple 2 criteria lookup on start and end times in the history table.  The following article introduces that simple but frequently overlooked simplicity.

    https://www.sqlservercentral.com/articles/finding-%e2%80%9cactive%e2%80%9d-rows-for-the-previous-month-sql-spackle-1

     

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply