Home Dashboard Directory Help
Search

Provide a graphical interface to the SQL Server Agent job scheduler and history by John Paul Cook


Status: 

Active


90
2
Sign in
to vote
Type: Suggestion
ID: 524854
Opened: 1/13/2010 7:29:12 PM
Access Restriction: Public
1
Workaround(s)
view

Description

It is very difficult to understand SQL Server Agent scheduled job schedules when there are many of them. Starting times of jobs are in text. Job history is also in textual form. When there are many jobs, the DBA is drowns in a sea of data devoid of information. The Outlook Calendar does a great job of showing overlaps and conflicts from people's calendars when scheduling a meeting for a group of people. SQL Server needs a graphical tool similar to that. There is a free tool http://www.sqlsoft.co.uk/sqljobvis.php that provides a lot of clarity for completed and running jobs.
Details
Sign in to post a comment.
Posted by Microsoft on 6/14/2013 at 10:57 AM
Hello,

Thank you for suggesting this change. We appreciate the feedback and the discussion associated. Unfortunately, there are tough decisions we need to make sometimes, so I would like to let you know that we won't be able to take this request into upcoming SQL Server release. We might reconsider it for one of the future releases, however.

The main reason why we are not taking it now is because making feature that will be useful for you requires amount of effort that doesn't fit into constraints we have for the upcoming release.

However, there is a workaround exists for those who think needs the feature. There is a Event Manager product from SQL Sentry company that looks to be perfect fit for what you are asking for in this discussion. You can find more information about this product here: http://www.sqlsentry.com/event-manager/sql-server-enterprise.asp

Thank you again for the feedback. We rely on your input a lot in improving our products and appreciate all input hugely.

Evgeny Krivosheev
SQL Server Program Manager
Posted by ALZDBA on 7/30/2010 at 1:00 AM
It would also be nice to have a GUI to actually manage the instances schedules.
Current situation is you get to the schedules via a job.
Maybe just providing a "schedules" branch in the SQLAgent object browser tree would enhance being able to actually manage schedules.
This is really needed for multi job schedules !
Posted by Smilee282000 on 2/19/2010 at 3:38 PM
We definitely need a tool that we can just look at real quick to see where scheduling conflicts are. Maybe have it ask for how much history you want to load from the log or something. Usually the last 24 hours is sufficient but sometimes you might want to see it for the week to see history trends. Maybe a job takes longer on Wednesday, for example, and I might want to schedule around it that day.

It would also be handy when something new is rolled into production & you need to figure out where the best time slot would be for a new job.
Posted by Courday Farnam1 on 2/15/2010 at 8:25 AM
Utilzing the Idera free SQL Job Agent schedule viewer currently. Would rather have an SSMS intragrated view/component.
Posted by John Paul Cook on 2/11/2010 at 6:23 AM
I disagree about the problems of being too user friendly. I used the simple, graphical output of SQLjobvis to show management how we had one server overtaxed with SQL Agent jobs. There is a need to show schedules in simple terms that management can understand. You can never be too user friendly when making a successful sales pitch to management.
Posted by antointhe on 2/11/2010 at 3:42 AM
Too user friendly would mean that every Joe would be in it (sorry to anyone named Joe out there! :)). You need to think about that Phil. Personally I'm usually fine with SQL Agent but have only used 2000 and 2005 agents to date - no call for 2008 yet.

In other words, if you are not used to it or trained in its use then perhaps you should not be accessing it until you understand it. I find that peer support and books / manuals are also good if the budget is small.
Posted by Catadmin on 2/5/2010 at 5:41 AM
We've gotten to the point where we just have too many jobs. Originally, they were spaced out so we wouldn't over lap them. Now we need to be able to see them in such a graphical representation so we can reschedule jobs as necessary, identify job depedencies, etc.

And seeing if a job is One Time or Reoccurring would also be nice.
Posted by mkj_710 on 2/1/2010 at 1:37 PM
I think johnpaulcook has a very good idea in representing jobs in graphs or timelines. we developers always think about the end user and how to make life easier for him. I think we have also to think about developers and make SQL more friendly and easy to understand
Posted by Microsoft on 1/25/2010 at 9:00 AM
Thank you for your feedback; we are considering improving Agent UI for our next release and we will take your comments into consideration.

Thanks,

Amy Lewis
Posted by Phil Brammer on 1/18/2010 at 8:50 AM
Even having a graphical display of Agent Jobs in a timeline would be a huge tool for administrators. The ability to use it to quickly balance the Agent load so as to avoid overlapping jobs, for instance, is one such use of the proposed tool.

Ideally, there are two views - one that shows scheduled times and average run lengths, and another that shows past execution history. Something like the Session Monitor in Informatica even.

I also support the ability to edit job schedules via the GUI, though I understand the complexities with such a diverse job schedule types (recurring, one time, etc...)
Sign in to post a workaround.
Posted by Microsoft on 6/13/2013 at 12:29 PM
Hello,

Thank you for suggesting this change. We appreciate the feedback and the discussion associated. Unfortunately, there are tough decisions we need to make sometimes, so I would like to let you know that we won't be able to take this request into upcoming SQL Server release. We might reconsider it for one of the future releases, however.

The main reason why we are not taking it now is because making feature that will be useful for you requires amount of effort that doesn't fit into constraints we have for the upcoming release.

However, there is a workaround exists for those who think needs the feature. There is a Event Manager product from SQL Sentry company that looks to be perfect fit for what you are asking for in this discussion. You can find more information about this product here: http://www.sqlsentry.com/event-manager/sql-server-enterprise.asp

Thank you again for the feedback. We rely on your input a lot in improving our products and appreciate all input hugely.

Evgeny Krivosheev
SQL Server Program Manager