Study guide
11.1 Schedules for Regular Maintenance Jobs
DP-300: Administering Microsoft Azure SQL Solutions Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current DP-300 Exam Facts 1.2 Skills Outline and Domain Weights 1.3 Study Strategy and Official Resources
2 Planning and Deploying Azure SQL Solutions
2.1 Choosing and Deploying Azure SQL Database Offerings 2.2 Automated Deployment, Azure Arc, and SQL Database in Microsoft Fabric 2.3 Table Partitioning and Sharding Strategy 2.4 Hybrid SQL Server and IaaS Patching
3 Configuring Resources for Scale and Performance
3.1 Configuring Azure SQL Database for Scale and Performance 3.2 Configuring Azure SQL Managed Instance for Scale and Performance 3.3 Configuring SQL Server on Azure VMs for Scale and Performance 3.4 Configuring Table Partitioning and Data Compression
4 Planning and Implementing a Migration Strategy
4.1 Evaluating Migration Requirements and Strategies 4.2 Implementing Online, Offline, and Azure Migrations 4.3 Migrating Between Azure SQL Services and Troubleshooting
5 Configuring Database Authentication and Authorization
5.1 Microsoft Entra ID Authentication for Azure SQL 5.2 Authentication for SQL on Azure VMs and Managed Instance; Troubleshooting 5.3 Security Principals and Entra-Backed Users 5.4 Permissions, Least Privilege, and T-SQL Management
6 Implementing Security for Data at Rest and in Transit
6.1 Transparent Data Encryption and Object-Level Encryption 6.2 Always Encrypted and VBS Enclaves 6.3 Firewall Rules, Private Links, and Service Endpoints
7 Implementing Compliance Controls for Sensitive Data
7.1 Data Classification and Server/Database Auditing 7.2 Change Data Tracking and Dynamic Data Masking 7.3 Row-Level Security and Ledger in Azure SQL
8 Monitoring Resource Activity and Performance
8.1 Operational Baselines and Performance Metric Sources 8.2 Interpreting Metrics and Configuring Activity Monitoring 8.3 Monitoring with Database Watcher (Preview) 8.4 Monitoring with Extended Events
9 Monitoring and Optimizing Query Performance
9.1 Configuring and Monitoring with Query Store 9.2 Session Blocking and Dynamic Management Views 9.3 Index Changes and Execution Plan Review 9.4 Query Construct Modifications and Intelligent Insights
10 Configuring Database Solutions for Optimal Performance
10.1 Index, Statistics, and Integrity Maintenance 10.2 Automatic Tuning and Database-Scoped Configuration 10.3 Server Settings and Resource Governor 10.4 Compute/Storage Scaling and Intelligent Query Processing
11 Creating and Managing SQL Server Agent Jobs
11.1 Schedules for Regular Maintenance Jobs 11.2 Job Alerts, Notifications, and Agent Troubleshooting 11.3 Automating Deployment with ARM and Bicep Templates
12 Automating Deployments and Database Tasks in Azure
12.1 Azure PowerShell, Azure CLI, and Deployment Monitoring 12.2 Elastic Jobs for Cross-Database Automation 12.3 Azure Automation Runbooks, Alerts, and Troubleshooting Automated Tasks
13 Planning an HA/DR Strategy and Backup and Restore
13.1 Recommending HA/DR Strategy from RPO and RTO 13.2 Hybrid and Azure-Specific HA/DR Solutions and Testing 13.3 Backup and Restore Strategy with Native Tools 13.4 Point-in-Time Restore and Recovery Operations
14 Configuring HA/DR: Long-Term Retention, Geo-Replication, and Failover Groups
14.1 Long-Term Retention, T-SQL Backup/Restore, and Cloud Storage 14.2 Active Geo-Replication 14.3 Failover Groups
15 Advanced HA/DR: Availability Groups, FCIs, Log Shipping, and Troubleshooting
15.1 Always On Availability Groups on SQL Managed Instance and Azure VMs 15.2 Always On Failover Cluster Instances and Log Shipping 15.3 Monitoring and Troubleshooting HA/DR Solutions
11.1 Schedules for Regular Maintenance Jobs
Key Takeaways Explain This Topic AI
SQL Server Agent is available in SQL Server on Azure VMs and Azure SQL Managed Instance, but NOT in Azure SQL Database single databases (use elastic jobs there instead)
A job is a container of one or more steps; each step targets a subsystem (T-SQL, SSIS, PowerShell, CmdExec, Analysis Services) and specifies on-success and on-failure actions plus retry attempts and retry interval
Schedules can be one-time or recurring daily/weekly/monthly with start and end dates, frequency, and an optional end date; a single shared schedule can drive many jobs
On Azure SQL Managed Instance, most SQL Server Agent features are supported but a few have caveats - Database Mail is supported, but some subsystems and external integrations behave differently than on a SQL Server VM
Schedule common maintenance (index rebuilds, statistics updates, backups, DBCC checks) as recurring weekly or nightly jobs, attaching them to shared schedules for consistent maintenance windows
Last updated: August 2026
Why SQL Server Agent Matters for DP-300
Domain 4 of the DP-300 exam covers "Configure and manage automation of tasks," worth roughly 15-20% of the exam. SQL Server Agent is the core engine behind that automation on two of the three Azure SQL deployment targets: SQL Server on Azure Virtual Machines and Azure SQL Managed Instance (SQL MI) . On Azure SQL Database single databases and elastic pools, Agent does not exist at all; that platform automates backups, index tuning, and statistics, and you handle custom automation with elastic jobs . Remembering this platform split is the single most heavily tested fact in this area.
SQL Server Agent Architecture
SQL Server Agent is a Windows service running alongside the SQL Server database engine. The exam lists six building blocks you should be able to define:
- Component Purpose
- Agent engine The service that owns job execution, monitors schedules, and raises alerts
- Jobs A named container of one or more steps, owned by a login, that runs on a schedule or on demand
Job steps Individual units of work, each targeting a subsystem (T-SQL, SSIS, PowerShell, CmdExec, Analysis Services, and others)
- Schedules The date/time rules that trigger a job to start
- Operators People or distribution lists who receive notifications
- Proxies Security principals that define the credential a step runs under, mapping to subsystems
All of these objects live in the msdb system database, which is why msdb health and its backup matter to Agent operations. The Agent service account (or, on Managed Instance, the equivalent platform-managed identity) needs permissions to do its work; job step execution then runs under either the Agent service account or, for elevated or isolated steps, under a proxy backed by a SQL Server credential.
Job Types and Subsystems
A job step targets one of several subsystems . The most common is T-SQL , which runs a Transact-SQL batch against a target database. Other subsystems include SQL Server Integration Services (SSIS) for ETL packages, PowerShell for scripting against the SqlServer and SqlServerSQLProvider modules, CmdExec for running operating-system executables, and Analysis Services (AS) commands and queries for AS processing tasks. The subsystem you pick on the step's Advanced page dictates which options are available; for example, T-SQL steps let you set the database and output file, while SSIS steps let you pick a package, configuration, and server. On the exam, the subsystem selection is often the answer when a scenario describes running a package, a script, or a native executable.
Job Steps and Flow Control
Each step has its own Advanced settings for flow control:
On success action : Go to the next step (default), Quit the job reporting success , Quit the job reporting failure , or Go to a specific step (enabling branching and loops).
On failure action : same four choices; the default is Quit the job reporting failure . A common pattern is to retry a transient failure by jumping to a logging step and then quitting.
Retry attempts : an integer; the step is retried up to this many times before the on-failure action fires.
Retry interval : seconds between retries.
A job can also have a target server (in multi-server environments using a master/target server (MSX/TSX) topology), but for DP-300 the scope is single-instance jobs. Job activity is visible in the Job Activity Monitor in SSMS and in the msdb.dbo.sysjobs , sysjobsteps , sysjobschedules , and sysjobhistory catalog views.