This topic describes how to create and define a Microsoft SQL Server Agent job step that uses an executable program or operating system command.
.gif) Note: |
|---|
|
By default, only members of the sysadmin fixed server role can create CmdExec job steps. These job steps run under the context of the SQL Server Agent service account unless the sysadmin user creates a proxy account. Users who are not members of the sysadmin role can create CmdExec job steps if they have access to a CmdExec proxy account.
|
To create a CmdExec job step
-
In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance.
-
Expand SQL Server Agent, create a new job or right-click an existing job, and then click Properties.
For more information about creating a job, see Creating Jobs.
-
In the Job Properties dialog, click the Steps page, and then click New.
-
In the New Job Step dialog, type a job Step name.
-
In the Type list, choose Operating system (CmdExec).
-
In Run as list, select the proxy account with the credentials that the job will use. By default, CmdExec job steps run under the context of the SQL Server Agent service account.
-
In the Process exit code of a successful command box, enter a value from 0 to 999999.
-
In the Command box, enter the operating system command or executable program.
-
Click the Advanced page to set job step options, such as: what action to take if the job step succeeds or fails, how many times SQL Server Agent should try to execute the job step, and the file where SQL Server Agent can write the job step output. Only members of the sysadmin fixed server role can write job step output to an operating system file.
See Also