u/patrickGuyInACube

First off… thank you all for the responses on my SQL Server Agent post. Seriously, I learned a ton from that thread.

One thing that came up a few times was Elastic Jobs, and I realized I honestly don’t have a great feel yet for how people are using them in the real world today.

So now I’m curious…

What are you using Elastic Jobs for today?

• Large scale maintenance?
• Multi-tenant SaaS environments?
• Cross-database orchestration?
• Centralized job management?
• Something completely different?

Also curious:

• What problems do Elastic Jobs solve really well?
• Where do they still fall short?
• What made you choose Elastic Jobs over SQL Server Agent, Airflow, Kubernetes CRON jobs, PowerShell, etc.?

And of course…

If Microsoft handed you a magic wand for Elastic Jobs, what’s the first thing you’d fix?

Alright SQL community… educate Patrick. What’s really happening in production?

Yooo! Allow me to re-introduce myself… my name is Patrick.

It’s been a minute since I’ve been deep in the SQL Server world. Back in my DBA days, SQL Server Agent was everywhere:

• backups
• maintenance
• ETL jobs
• alerts
• scheduled scripts
• and honestly… everything else too

So now I’m curious…

What are you using SQL Server Agent for today?

What’s working so well you’d say “don’t touch it”?

What still feels clunky, painful, or way too manual?

Have you moved away from it completely? If so, what changed?

And if Microsoft handed you a magic wand for SQL Server Agent… what’s the first thing you’d fix?

Would love to hear what real-world SQL Server operations actually look like today.

And honestly… thanks in advance for the trip down memory lane.