When assessing the two solutions, reviewers found ActiveBatch easier to use and do business with overall. However, reviewers preferred the ease of set up with Azure Batch, along with administration.
Reviewers felt that ActiveBatch meets the needs of their business better than Azure Batch.
When comparing quality of ongoing product support, reviewers felt that ActiveBatch is the preferred option.
For feature updates and roadmaps, our reviewers preferred the direction of ActiveBatch over Azure Batch.
Pricing
Entry-Level Pricing
ActiveBatch
Simple, Usage-Based Pricing
Contact Us
Ease of use - connect to your entire tech stack with our low-code API adapter and no-code connectors for SQL Server, SharePoint, Informatica, ServiceNow, VMware and more.
Outstanding out-of-the-box features, including predictive SLA, change management, auto-remediation and a complete managed transfer file suite.
Monitoring, alerting and reporting - reduce time troubleshooting and manage dependencies better with flexible and customizable monitoring and alerting.
What is the best way to retain 10 days of log information on each job. This is one area where the documentation can use recommendations. For example, I want to see how the job performed, via the log, from 10 days ago. Today, the log would show GetFile failed if older than three days, or thereabouts.
1 Comment
KW
All jobs have properties that determine how job log files are managed. The factory default setting is Centrally Managed Logging. This means that the location...Read more
What is the best way to retain 10 days of log information on each job?
1 Comment
NA
create a log file instead of having active batch manage it,Read more
With over 3 million reviews, we can provide the specific details that help you make an informed software buying decision for your business. Finding the right product is important, let us help.