Compartilhar via


Classe VariableDispenser

Accesses the Variables collection during package execution. This class cannot be inherited.

Hierarquia de herança

System. . :: . .Object
  Microsoft.SqlServer.Dts.Runtime. . :: . .DtsObject
    Microsoft.SqlServer.Dts.Runtime..::..VariableDispenser

Namespace:  Microsoft.SqlServer.Dts.Runtime
Assembly:  Microsoft.SqlServer.ManagedDTS (em Microsoft.SqlServer.ManagedDTS.dll)

Sintaxe

'Declaração
Public NotInheritable Class VariableDispenser _
    Inherits DtsObject
'Uso
Dim instance As VariableDispenser
public sealed class VariableDispenser : DtsObject
public ref class VariableDispenser sealed : public DtsObject
[<SealedAttribute>]
type VariableDispenser =  
    class
        inherit DtsObject
    end
public final class VariableDispenser extends DtsObject

O tipo VariableDispenser expõe os membros a seguir.

Métodos

  Nome Descrição
Método público Contains Specifies whether an item can be retrieved from the VariableDispenser collection by using indexing without throwing an exception.
Método público Equals Determines whether two object instances are equal. (Herdado de DtsObject.)
Método protegido Finalize (Herdado de Object.)
Método público GetHashCode Returns the hash code for this instance. (Herdado de DtsObject.)
Método público GetQualifiedName Returns the qualified name of the variable.
Método público GetType (Herdado de Object.)
Método público GetVariables Locks the variables that are in the read-only list and the read/write list.
Método público LockForRead Adds the variable to the list of variables to be locked for read-only access.
Método público LockForWrite Adds the variable to the list of variables to be locked for read/write access.
Método público LockOneForRead Puts the variable in a list, and then locks it for read-only access.
Método público LockOneForWrite Puts the variable in a list, and then locks it for read/write access.
Método protegido MemberwiseClone (Herdado de Object.)
Método público Reset Clears both the read-only list and read/write list when the call to GetVariables fails.
Método público ToString (Herdado de Object.)

Início

Comentários

There are two scenarios for using the variable dispenser.

  1. You want just one variable. In this scenario, call LockOneForRead or LockOneForWrite, and a collection with one element is returned.

  2. You want several variables. In this scenario, call LockForRead and LockForWrite several times, one for each variable. This builds up two lists, one list that contains variables for reading and one list that contains variables for writing. Next, call GetVariables, which gives you a collection that contains all of the locked variables. If GetVariables succeeds, the two lists, which are the lists of variable names, not actual locks, are cleared.

To explicitly release the locks, call Unlock on the collection. This method unlocks the variables themselves. If GetVariables fails, the lists remain unchanged, and you can call GetVariables again. If you still do not succeed in obtaining the variables, call Reset to clear the lists and bring the variable dispenser back to its initial state.

The Variables collection contains a Locked property that indicates whether a variable dispenser collection of variables is locked (true) or unlocked (false). The reason to review this property is that some tasks explicitly release locks to the variables they are using, and calling Unlock twice throws an error. Therefore, you should use this property to determine whether the dispensed collection is locked before calling Unlock.

Observação importanteImportante

The VariableDispenser is used with the Runtime classes. If you are using data flow components (Microsoft.SqlServer.Dts.Pipeline), then you may be required to use the IDTSVariableDispenser100 instead. To know which variable dispenser to use, see the documentation for the object you are acquiring variables on, and verify the return object of the method.

Segurança de thread

Qualquer membro público static (Shared no Visual Basic) desse tipo é seguro para threads. Não há garantia de que qualquer membro de instância seja seguro para threads.

Consulte também

Referência