Let’s face it. Scheduling batch jobs with native batch automation tools isn’t easy, or flexible. Whether you’re wrestling with the complex format of cron, or dealing with the limited features in Windows Task Scheduler or SQL Agent, it is never as easy as 1-2-3. Let’s break down some real-world examples of scheduling batch jobs with
Yvette Carpenter is the technical operations manager for a financial services firm that spun off from another company in 2016. Before the transition, the company wasn’t using true enterprise scheduling solutions, and Carpenter was tasked with automating a great number of manual processes. After evaluating potential automation partners, the company selected JAMS, a centralized workload
The latest build of JAMS V7 provides users with a new database option – Azure SQL. For most enterprises, SQL, or even SQL Express, has plenty of horsepower to handle data on the back end of JAMS. We specifically designed JAMS to consume as few resources as possible – an efficient database structure, small payloads,
If you’ve experienced blocking or have been tempted to allow non-administrators to run batch jobs on your database, that’s exactly how the conversation might start. More likely, though, you’re reading this because your organization is growing, either in scale or complexity, and you need to break workload automation away from the limits imposed by native