On Azure SQL Database Managed Instance, most, but not all SQL Server Agent features are currently supported. See Azure SQL Database Managed Instance T-SQL differences from SQL Server for details.
A job is a specified series of operations performed sequentially by SQL Server Agent. A job can perform a wide range of activities, including running Transact-SQL scripts, command prompt applications, Microsoft ActiveX scripts, Integration Services packages, Analysis Services commands and queries, or Replication tasks. Jobs can run repetitive or schedulable tasks, and they can automatically notify users of job status by generating alerts, thereby greatly simplifying SQL Server administration.
To create a job, a user must be a member of one of the SQL Server Agent fixed database roles or the sysadmin fixed server role. A job can be edited only by its owner or members of the sysadmin role. Members of the sysadmin role can assign job ownership to other users, and they can run any job, regardless of the job owner. For more information about the SQL Server Agent fixed database roles, see SQL Server Agent Fixed Database Roles.
Jobs can be written to run on the local instance of SQL Server or on multiple instances across an enterprise. To run jobs on multiple servers, you must set up at least one master server and one or more target servers. For more information about master and target servers, see Automated Administration Across an Enterprise
SQL Server Agent records job and job step information in the job history.
|Describes how to create a SQL Server Agent job.||Create a Job|
|Describes how to reassign ownership of SQL Server Agent jobs to another user.||Give Others Ownership of a Job|
|Describes how to set up the SQL Server Agent job history log.||Set Up the Job History Log|