How do most DBA's graphically monitor 100's of nightly jobs to ensure there are not overlaps or conflicts of jobs running at the same time? I was thinking about using various tools, but thought I might just be inventing the wheel. I know this probably sounds like a fairly simple question, but I am someone who is new at the DBA effort. Thanks for any help you can lend in the area.
Requires Free Membership to View
Each DBA will answer this question in a slightly different way.
I'm still one of those "crusty old devils" that learned to deal with the character mode scheduling software, and for the most part still prefers it. The various GUI tools all have their own strong and weak points, but when the job absolutely, positively has to be done right, I still revert to the scheduler's native interface, which is text.
The Opalis robot has gotten some very good press. It works relatively smoothly, with relatively few nasty surprises awaiting the unsophisticated user. It can run on both Windows-NT and most of the (Unix derivative) operating systems that support CRON.
Windows-NT supports a quite functional, but kind of idiosyncratic scheduler. Microsoft provides a crude but effective command line schedule editor with NT called AT.EXE. They also provide a much easier to use GUI based tool with the NT Resource Kit.
While there are lots of scheduling tools, I still prefer to use whatever is provided with the operating system, and I try to stay as close to its "native interface" as possible, to minimize the number of "moving pieces" that I have to deal with!
For More Information
- What do you think about this answer? E-mail us at editor@searchDatabase.com with your feedback.
- The Best Database Design Web Links: tips, tutorials, scripts, and more.
- Have a Database Design tip to offer your fellow DBA's and developers? The best tips submitted will receive a cool prize--submit your tip today!
- Ask your technical Database Design questions--or help out your peers by answering them--in our live discussion forums.
- Ask the Experts yourself: Our Database Design guru is waiting to answer your toughest questions.
This was first published in May 2001
Join the conversationComment
Share
Comments
Results
Contribute to the conversation