Execute Method

WmiEventWatcherTask.Execute Method

Runs the task.

Namespace: Microsoft.SqlServer.Dts.Tasks.WmiEventWatcherTask
Assembly: Microsoft.SqlServer.WMIEWTask (in microsoft.sqlserver.wmiewtask.dll)

public override DTSExecResult Execute (
	Connections connections,
	VariableDispenser variableDispenser,
	IDTSComponentEvents events,
	IDTSLogging log,
	Object transaction
public DTSExecResult Execute (
	Connections connections, 
	VariableDispenser variableDispenser, 
	IDTSComponentEvents events, 
	IDTSLogging log, 
	Object transaction
public override function Execute (
	connections : Connections, 
	variableDispenser : VariableDispenser, 
	events : IDTSComponentEvents, 
	log : IDTSLogging, 
	transaction : Object
) : DTSExecResult



A Connections collection for the task.


A Variables collection for the task.


A reference to an object that implements the IDTSComponentEvents interface for raising events.


A reference to an object that implements IDTSLogging.


The transaction object that the task is part of, depending on the value found in the TransactionOption property. This value can be set to a null reference (Nothing in Visual Basic).

Return Value

A DTSExecResult that indicates the outcome of the execution.

The Execute method is inherited by task hosts and other objects from the Executable abstract class, through the DtsContainer class, and allows the inheriting objects to be run by the runtime engine. The Execute method inherited by the individual objects is not commonly used in code, and it is recommended that you call the Execute method if you need to run any of the tasks or containers in the package. However, the Execute method is available on individual objects should you find a unique circumstance where it is needed.

The main use of the Execute method is for it to be inherited and overridden when you create a custom task. For more information about how to override the Execute method, see Implementing the Execute Method in Custom Integration Services Tasks.

The Execute method calls the Validate method implicitly before the package runs. All tasks in the package are reviewed for appropriate settings during validation, and all objects in the package are reviewed, including the package, containers, and other components in the package.

If there are no problems encountered in the validation phase that would cause the package to fail, the package object proceeds to call the Execute method for each task and object in the package.

Pass null for the transaction parameter when the TransactionOption property is false. If the TransactionOption property is true, you can pass null in the transaction parameter to indicate that the container supports transactions but does not participate.

The following code example shows how to run a package containing a BulkInsertTask after some of the task properties are set. The Bulk Insert task is an example for this code sample; any task can be created in its place.

using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.SqlServer.Dts.Runtime;
using Microsoft.SqlServer.Dts.Tasks.BulkInsertTask

namespace Microsoft.SqlServer.SSIS.Samples
    class Program
        static void Main(string[] args)
            Package p = new Package();
            p.InteractiveMode = true;
            p.OfflineMode = true;
            Executable exec1 = pkg.Executables.Add("STOCK:BulkInsertTask");
            TaskHost th = exec1 as TaskHost;

            // Set the CheckConstraints and DataFileType properties.           
            th.Properties["CheckConstraints"].SetValue(th, true);
            th.Properties["DataFileType"].SetValue(th, DTSBulkInsert_DataFileType.DTSBulkInsert_DataFileType_Native);
            // Run the package that contains the task.

            // Review the results of the run.
            if (taskH.ExecutionResult == DTSExecResult.Failure || taskH.ExecutionStatus == DTSExecStatus.Abend)
                Console.WriteLine("Task failed or abended");
                Console.WriteLine("Task ran successfully");

Any public static (Shared in Microsoft Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Development Platforms

For a list of the supported platforms, see Hardware and Software Requirements for Installing SQL Server 2005.

Target Platforms

Community Additions

© 2015 Microsoft