Manage Jobs Across an Enterprise

Applies to: SQL Server Azure SQL Managed Instance

Important

On Azure SQL Managed Instance, most, but not all SQL Server Agent features are currently supported. See Azure SQL Managed Instance T-SQL differences from SQL Server for details.

If you make changes to multiserver job definitions outside Microsoft SQL Server Management Studio, you must post the changes to the download list so that target servers can download the updated job again. To ensure that target servers have current job definitions, post an INSERT instruction after you update the multiserver job, as follows:

EXECUTE sp_post_msx_operation 'INSERT', 'JOB', '<job id>'  

To notify target servers that a multiserver job has been modified, you must invoke the preceding command after using any of the following procedures:

• sp_add_jobstep (Transact-SQL)

• sp_update_jobstep (Transact-SQL)

• sp_delete_jobstep (Transact-SQL)

• Managing Events

• sp_detach_schedule (Transact-SQL)

  Note

  It is not necessary to call sp_post_msx_operation after you call sp_update_job or sp_delete_job, because these stored procedures post the required changes to the download list automatically.

The following are common tasks for managing jobs across an enterprise:

To check the status of a target server

• Transact-SQL

• SQL Server Management Objects (SMO)

To change the target servers for a job

• SQL Server Management Studio

• Transact-SQL

• SQL Server Management Objects (SMO)

To change the location of a target server

• SQL Server Management Studio

• Transact-SQL

• SQL Server Management Objects (SMO)

To synchronize target server clocks

• SQL Server Management Studio

• Transact-SQL

To force a target server to poll the master server

• SQL Server Management Studio

• Transact-SQL

See Also

Manage Events