Edit

Share via

sp_add_jobserver (Transact-SQL)

  • Article

Applies to: SQL Server

Targets the specified job at the specified server.

Transact-SQL syntax conventions

Syntax

sp_add_jobserver
    [ @job_id = ] job_id
        | [ @job_name = ] 'job_name'
    [ , [ @server_name = ] 'server' ]
[ ; ]

Arguments

[ @job_id = ] job_id

The identification number of the job. job_id is uniqueidentifier, with a default of NULL.

Either @job_id or @job_name must be specified, but both can't be specified.

[ @job_name = ] 'job_name'

The name of the job. job_name is sysname, with a default of NULL.

Either @job_id or @job_name must be specified, but both can't be specified.

[ @server_name = ] N'server'

The name of the server at which to target the job. @server_name is nvarchar(30), with a default of (LOCAL). @server_name can be either (LOCAL) for a local server, or the name of an existing target server.

Return code values

0 (success) or 1 (failure).

Result set

None.

Remarks

@automatic_post exists in sp_add_jobserver, but isn't listed under Arguments. @automatic_post is reserved for internal use.

SQL Server Management Studio provides an easy, graphical way to manage jobs, and is the recommended way to create and manage the job infrastructure.

Permissions

You can grant EXECUTE permissions on this procedure, but these permissions might be overridden during a SQL Server upgrade.

Other users must be granted one of the following SQL Server Agent fixed database roles in the msdb database:

  • SQLAgentUserRole
  • SQLAgentReaderRole
  • SQLAgentOperatorRole

For details about the permissions of these roles, see SQL Server Agent Fixed Database Roles.

Only members of the sysadmin fixed server role can execute sp_add_jobserver for jobs that involve multiple servers.

Examples

A. Assign a job to the local server

The following example assigns the job NightlyBackups to run on the local server.

Note

This example assumes that the NightlyBackups job already exists.

USE msdb;
GO

EXEC dbo.sp_add_jobserver @job_name = N'NightlyBackups';
GO

B. Assign a job to run on a different server

The following example assigns the multiserver job Weekly Sales Backups to the server SEATTLE2.

Note

This example assumes that the Weekly Sales Backups job already exists and that SEATTLE2 is registered as a target server for the current instance.

USE msdb;
GO

EXEC dbo.sp_add_jobserver @job_name = N'Weekly Sales Backups',
    @server_name = N'SEATTLE2';
GO

Related content