Chat now with support
Chat with Support

LiteSpeed for SQL Server 8.9.5 - Security and Compliance Guide

Describe Job Steps

You must enter at least one step to create a valid job. If you do not enter a second step, the last step action is set to Quit with success.

NOTE: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions.

To describe a job step

  1. In the Steps page, open an existing step or click New to add a new job step. Review the following for additional information:

    Start step

    Select the step where you want to start the job. Use this option to start a job beginning at a step other than the first step.

    If you begin with a step other than the first step of the job, a warning message displays.

    Insert

    Select a job step and click Insert to create a new step and insert it before the selected step.

  2. Define the job step options and review the following for additional information:

    Step type

    Select one of the following types of steps to execute:

    • Transact-SQL Script (T-SQL)—Executes T-SQL batches.
    • ActiveX Script—Executes ActiveX scripts written in Visual Basic, Java Script, or any supported ActiveX script language.
    • Operating System (CmdExec)—Executes any commands or programs that have extensions ending with .bat, .cmd, .com, or .exe.
    • Replication Distributor—Executes the Distribution Agent automatically, if a distribution job was created.
    • Replication Transaction-Log Reader—Executes the Log Reader Agent.
    • Replication Merge—Executes the Merge Agent automatically, if a merge job was created.
    • Replication Queue Reader—Executes the Queue Reader Agent automatically, if a queue reader job was created.
    • Replication Snapshot—Executes the Snapshot Agent automatically, if a snapshot job was created.
    • Analysis Services Query—Executes a multidimensional expressions (MDX) query on an OLAP server.
    • Analysis Services Command —Executes an XML command on an OLAP server.
    • SSIS Package Execution Subsystem—Executes a single SSIS package. You must create a separate job step for each package.
    • PowerShell Subsystem—Executes the Microsoft task automation and configuration management framework, consisting of a command-line shell and associated scripting language built on the .NET Framework.
  3. Click Advanced to specify actions to take when the step completes.

    On success action

    Select an action to perform when the selected job step successfully completes. The default is to go to the next step.

    On failed action

    Select an action to perform if the step fails. The default is to quit the job and report the failure.

    Retry attempts

    Enter the number of times to retry the job step if it fails.

    Retry interval

    Enter the number of minutes that should elapse before attempting to re-execute the job step.

    Append script to step history

    For T-SQL, select this checkbox to add the script statements to the job step history. This information displays when you edit a job or view job history.

 

Related Topic

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating