Udostępnij za pośrednictwem


Execute SQL Task Editor (General Page)

Use the General page of the Execute SQL Task Editor dialog box to configure the Execute SQL task and provide the SQL statement that the task runs.

To learn about running SQL statements in packages, see Execute SQL Task and Transact-SQL Reference (Transact-SQL).

Static Options

  • Name
    Provide a unique name for the Execute SQL task in the workflow. The name that is provided will be displayed within SSIS Designer.
  • Description
    Describe the Execute SQL task. As a best practice, to make packages self-documenting and easier to maintain, describe the task in terms of its purpose.
  • TimeOut
    Specify the maximum number of seconds the task will run before timing out. A value of 0 indicates an infinite time. The default is 0.

    Note

    Stored procedures do not time out if they emulate sleep functionality by providing time for connections to be made and transactions to complete that is greater than the number of seconds specified by TimeOut. However, stored procedures that execute queries are always subject to the time restriction specified by TimeOut.

  • CodePage
    Specify the code page to use when translating Unicode values in variables. The default value is the code page of the local computer.
  • ResultSet
    Specify the result type expected by the SQL statement being run. Choose among Single row, Full result set, XML, or None.
  • Connection
    Choose the connection from a list of defined connection managers. To create a new connection, select <New connection...>.
  • SQLSourceType
    Select the source type of the SQL statement that the task runs.

    Depending on the connection manager type that Execute SQL task uses, you must use specific parameter markers in parameterized SQL statements.

    Related Topics: Running Parameterized SQL Commands section in Execute SQL Task

    This property has the options listed in the following table.

    Value Description

    Direct input

    Set the source to a Transact-SQL statement. Selecting this value displays the dynamic option, SQLStatement.

    File connection

    Select a file that contains a Transact-SQL statement. Setting this option displays the dynamic option, FileConnection.

    Variable

    Set the source to a variable that defines the Transact-SQL statement. Selecting this value displays the dynamic option, SourceVariable.

  • QueryIsStoredProcedure
    Indicates whether the specified SQL statement to be run is a stored procedure. This property is read/write only if the task uses the ADO connection manager. Otherwise the property is read-only and its value is false.
  • BypassPrepare
    Indicate whether the SQL statement is prepared. true skips preparation; false prepares the SQL statement before running it. This option is available only with OLE DB connections that support preparation.

    Related Topics: Prepared Execution

  • Browse
    Locate a file that contains a SQL statement by using the Open dialog box. Select a file to copy the contents of the file as a SQL statement into the SQLStatement property.
  • Build Query
    Create an SQL statement using the Query Builder dialog box, a graphical tool used to create queries. This option is available when the SQLSourceType option is set to Direct input.
  • Parse Query
    Validate the syntax of the SQL statement.

SQLSourceType Dynamic Options

SQLSourceType = Direct input

  • SQLStatement
    Type the SQL statement to execute in the option box, or click the browse button (…) to type the SQL statement in the Enter SQL Query dialog box, or click Build Query to compose the statement using the Query Builder dialog box.

    Related Topics:Query Builder

SQLSourceType = File connection

SQLSourceType = Variable

See Also

Reference

Execute SQL Task Editor (Parameter Mapping Page)
Execute SQL Task Editor (Result Set Page)

Other Resources

Integration Services Error and Message Reference
Accessing and Changing Database Data

Help and Information

Getting SQL Server 2005 Assistance

Change History

Release History

5 December 2005

New content:
  • Added information about parameter markers in parameterized SQL statements.