JAMS for the win
Use Cases and Deployment Scope
The N-tier application we use has jobs coming from multiple servers 24 hours a day. JAMS manages all of those and allows us to set alerts, to set automatic retires and send notifications. The history is fantasic way to get a quick view of what failed over the day without checking every job. There are so many funtionalities we have yet to use, such as running sql jobs or CMD scripts. Fantasic product, highly recommended.
Pros
- history
- alerts
- auto-resubmits
Cons
- a wizard for setting up jobs
- a folder with the failed job notifications, easy to find
- an easier way to set web interface (back to the wizard)
- a set of video walk throughs with examples for each type of scheduling
Return on Investment
- The ROI is unquestionable, I cannot imagine life without it
- Reliability is top notch, haven't seen it crash in 15 years of use
- As for resources, it has a small footprint on the server
Alternatives Considered
Microsoft To Do
Other Software Used
Microsoft SQL Server, Microsoft IIS, Microsoft 365








