Instiq
Chapter 4 · Configure and Manage Automation of Tasks·v2.0.0·Updated 6/3/2026·~9 min

What's changed: Deepened DP-300 Chapter 4 (ja figures; comparison tables/scenarios/FAQ/traps/deep paragraphs in all sections)

4.1Automating Tasks with Jobs

Key points

Understand ways to automate routine operations—SQL Server Agent (VM/Managed Instance), Elastic Jobs (Azure SQL Database, across many DBs), and Azure Automation. The mechanism depends on the deployment.

Automate routine tasks like backup checks, statistics updates, and index rebuilds—but the available mechanism differs by deployment (SQL Database vs MI/VM).

4.1.1Automation mechanisms

Diagram showing automation per deployment: SQL Server on VM / Managed Instance can use SQL Server Agent (jobs, schedules, notifications). Azure SQL Database has no SQL Agent, so use Elastic Jobs (scheduled execution across many DBs). Across all, Azure Automation (runbooks) and Logic Apps can orchestrate.
Automation by deployment
  • SQL Server Agent: a job scheduler available on VM / Managed Instance (jobs, schedules, notifications).
  • Elastic Jobs: since Azure SQL Database lacks SQL Agent, run jobs across many DBs.
  • Azure Automation: automate broader Azure operations via runbooks (e.g., PowerShell).
  • Typical tasks: update statistics, rebuild indexes, integrity checks, backup verification, etc.
Exam point

Common on DP-300: VM/MI job automation = SQL Server Agent, Azure SQL Database lacks SQL Agent → Elastic Jobs, scheduled execution across many DBs = Elastic Jobs, broad Azure automation = Azure Automation. Watch that the choice depends on deployment.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.