JAMS Pros and Cons

Before JAMS we had a hodge podge of powershell scripts run by windows task scheduler strewn across our environment. With JAMS we were able to centralize our automation and maintenance tasks with built in Success/Failure notifications with logging.

The suite of Powershell cmdlets which allow querying the credential manager, import/export jobs and their respective scripts that enabled us to easily check our code into git, as well as the ability to transmit files via multiple file transfer protocols.

Another thing we love is the credential manager. This may be the biggest boon for us, securely managing passwords was a struggle for us beforehand.

Couldn't be happier with the product, it has solved a lot of headaches.

Support on the product has also been very helpful. There has not been an issue that they were not able to assist in solving. Their support staff are quick to respond and very courteous. Review collected by and hosted on G2.com.

There have been no downsides that we have experienced. JAMS has met our needs well. Review collected by and hosted on G2.com.

It helps us in our operation to fulfill the customer's wishes Review collected by and hosted on G2.com.

Nothing. It fullfills in all our possibilities. Review collected by and hosted on G2.com.

The most useful feature we found is scheduling of job(s) based on workflow. In which critical business jobs are scheduled and executes in sequence. Without workflow feature we may have to create no of independent jobs. Review collected by and hosted on G2.com.

There's none downside of JAMS scheduler. Though with any software/suite there's always room for new features.

Eg: JAMS web client is not as good as desktop client to create complex jobs. Review collected by and hosted on G2.com.

It's easy to install and configure and troubleshoot the problems ourselves. Review collected by and hosted on G2.com.

Hmm, none actually, everything seems advantageous as per your need. Review collected by and hosted on G2.com.

All the jobs will be in one place when we finish. And tech support is all important, and you've nailed it. The error I had was very strange, and required SQL Server permissions as well as running the command in the command line to debug. I am confident that if we have this response when it is still in test, I have no qualms about if we have a Production job issue. Review collected by and hosted on G2.com.

I've found nothing to dislike so far. Your tech support is very responsive and thorough. They don't stop until there is a resolution. And I was skeptical to trust they would help, but the response was really good. Review collected by and hosted on G2.com.

The JAMS automation systems are very intuitive. All our system administrators and developers compliment how well it is to work with the systems. Review collected by and hosted on G2.com.

The only issue or concern I've had in the past is the slow install and larger-then-normal client installation. Over a gig storage is a bit hefty for a client interface. Hoping future SFTP frameworks are more fortified in the application so we can better transition off of WinSCP setups without so much programming. Other than that, no complaints. Review collected by and hosted on G2.com.

Th support team connects very quickly and so helpful while arranging the meetings.

Gennaro Piccolo the Jams support agent help me all the way to finish my task very quickly as well as he provided all possible solutions and help me to write new scripts as needed. Review collected by and hosted on G2.com.

So far so good, it is integrated with most of the tools, due to that i cannot really say any dislikes about Jams enterprise scheduler. Review collected by and hosted on G2.com.

User friendly and easy to use and feature rich scheduler i have ever came across. Review collected by and hosted on G2.com.

Not much.. if it good if we get cloud JAMS solution , if not yet Review collected by and hosted on G2.com.

1. The historical view of what jobs ran across all environment.

2. For the SSIS part, before when it was scheduled as a SQL Agent job to run the SSIS, we look in the history of the job only to be redirected to the SSISDB Catalog. Now, with the SSISDirect, we can see the log (as part of the notification), but if too big of a log, we can just go to the JAMS Desktop and see the execution log.

3. The Maintenance window. If all the jobs are already migrated to JAMS, set the maintenance window once, and you can be sure that nothing will run until that is lifted. Review collected by and hosted on G2.com.

It looks like JAMS still has a lot of untapped potential. We haven't really looked at all it can do although we are positive that there's still more. But, what I dislike is, cannot move a job from one folder to another (when we reorganize) without losing the historical execution information. Review collected by and hosted on G2.com.

Really flexible and highly configurable. Review collected by and hosted on G2.com.

It can get confusing, not intuitive, need to reference to the manual. Review collected by and hosted on G2.com.