TransactionScope.Complete 메서드

정의

네임스페이스:

System.Transactions

어셈블리:

System.Transactions.Local.dll

Source:

TransactionScope.cs

범위의 모든 작업이 성공적으로 완료되었음을 나타냅니다.

public:
 void Complete();

public void Complete ();

member this.Complete : unit -> unit

Public Sub Complete ()

예외

InvalidOperationException

이 메서드가 이미 한 번 호출된 경우

예제

다음 예제에서는 사용 TransactionScope 하는 방법에 설명 합니다 클래스는 트랜잭션에 참여 하는 코드 블록을 정의 합니다.

// This function takes arguments for 2 connection strings and commands to create a transaction 
// involving two SQL Servers. It returns a value > 0 if the transaction is committed, 0 if the 
// transaction is rolled back. To test this code, you can connect to two different databases 
// on the same server by altering the connection string, or to another 3rd party RDBMS by 
// altering the code in the connection2 code block.
static public int CreateTransactionScope(
    string connectString1, string connectString2,
    string commandText1, string commandText2)
{
    // Initialize the return value to zero and create a StringWriter to display results.
    int returnValue = 0;
    System.IO.StringWriter writer = new System.IO.StringWriter();

    try
    {
        // Create the TransactionScope to execute the commands, guaranteeing
        // that both commands can commit or roll back as a single unit of work.
        using (TransactionScope scope = new TransactionScope())
        {
            using (SqlConnection connection1 = new SqlConnection(connectString1))
            {
                // Opening the connection automatically enlists it in the 
                // TransactionScope as a lightweight transaction.
                connection1.Open();

                // Create the SqlCommand object and execute the first command.
                SqlCommand command1 = new SqlCommand(commandText1, connection1);
                returnValue = command1.ExecuteNonQuery();
                writer.WriteLine("Rows to be affected by command1: {0}", returnValue);

                // If you get here, this means that command1 succeeded. By nesting
                // the using block for connection2 inside that of connection1, you
                // conserve server and network resources as connection2 is opened
                // only when there is a chance that the transaction can commit.   
                using (SqlConnection connection2 = new SqlConnection(connectString2))
                {
                    // The transaction is escalated to a full distributed
                    // transaction when connection2 is opened.
                    connection2.Open();

                    // Execute the second command in the second database.
                    returnValue = 0;
                    SqlCommand command2 = new SqlCommand(commandText2, connection2);
                    returnValue = command2.ExecuteNonQuery();
                    writer.WriteLine("Rows to be affected by command2: {0}", returnValue);
                }
            }

            // The Complete method commits the transaction. If an exception has been thrown,
            // Complete is not  called and the transaction is rolled back.
            scope.Complete();
        }
    }
    catch (TransactionAbortedException ex)
    {
        writer.WriteLine("TransactionAbortedException Message: {0}", ex.Message);
    }

    // Display messages.
    Console.WriteLine(writer.ToString());

    return returnValue;
}

'  This function takes arguments for 2 connection strings and commands to create a transaction 
'  involving two SQL Servers. It returns a value > 0 if the transaction is committed, 0 if the 
'  transaction is rolled back. To test this code, you can connect to two different databases 
'  on the same server by altering the connection string, or to another 3rd party RDBMS  
'  by altering the code in the connection2 code block.
Public Function CreateTransactionScope( _
  ByVal connectString1 As String, ByVal connectString2 As String, _
  ByVal commandText1 As String, ByVal commandText2 As String) As Integer

    ' Initialize the return value to zero and create a StringWriter to display results.
    Dim returnValue As Integer = 0
    Dim writer As System.IO.StringWriter = New System.IO.StringWriter

    Try
    ' Create the TransactionScope to execute the commands, guaranteeing
    '  that both commands can commit or roll back as a single unit of work.
        Using scope As New TransactionScope()
            Using connection1 As New SqlConnection(connectString1)
                ' Opening the connection automatically enlists it in the 
                ' TransactionScope as a lightweight transaction.
                connection1.Open()

                ' Create the SqlCommand object and execute the first command.
                Dim command1 As SqlCommand = New SqlCommand(commandText1, connection1)
                returnValue = command1.ExecuteNonQuery()
                writer.WriteLine("Rows to be affected by command1: {0}", returnValue)

                ' If you get here, this means that command1 succeeded. By nesting
                ' the using block for connection2 inside that of connection1, you
                ' conserve server and network resources as connection2 is opened
                ' only when there is a chance that the transaction can commit.   
                Using connection2 As New SqlConnection(connectString2)
                    ' The transaction is escalated to a full distributed
                    ' transaction when connection2 is opened.
                    connection2.Open()

                    ' Execute the second command in the second database.
                    returnValue = 0
                    Dim command2 As SqlCommand = New SqlCommand(commandText2, connection2)
                    returnValue = command2.ExecuteNonQuery()
                    writer.WriteLine("Rows to be affected by command2: {0}", returnValue)
                End Using
            End Using

        ' The Complete method commits the transaction. If an exception has been thrown,
        ' Complete is called and the transaction is rolled back.
        scope.Complete()
        End Using
    Catch ex As TransactionAbortedException
        writer.WriteLine("TransactionAbortedException Message: {0}", ex.Message)
    End Try

    ' Display messages.
    Console.WriteLine(writer.ToString())

    Return returnValue
End Function

설명

scope 내의 모든 작업이 성공적으로 완료되면 이 메서드를 한 번만 호출하여 트랜잭션 관리자에게 모든 리소스의 상태가 일관되고 트랜잭션을 커밋할 수 있음을 알려야 합니다. 호출을 블록의 마지막 문 using 으로 두는 것이 매우 좋습니다.

이 메서드를 사용하는 방법에 대한 자세한 내용은 트랜잭션 범위를 사용하여 암시적 트랜잭션 구현 항목을 참조하세요.

트랜잭션 관리자가 이를 시스템 오류로 해석하거나 트랜잭션의 scope 내에서 throw된 예외로 해석하므로 이 메서드를 호출하지 않으면 트랜잭션이 중단됩니다. 그러나 이 메서드를 호출해도 트랜잭션의 커밋이 보장되지는 않습니다. 트랜잭션 관리자에게 상태를 알리는 방법일 뿐입니다. 이 메서드를 호출한 후에는 속성을 통해 앰비언트 트랜잭션에 Current 더 이상 액세스할 수 없으며 이렇게 하면 예외가 throw됩니다.

리소스 관리자 간의 실제 커밋 작업은 개체가 트랜잭션을 End Using 만든 경우 TransactionScope 문에서 발생합니다. 트랜잭션을 만들지 않은 경우에는 CommittableTransaction 개체 소유자가 Commit을 호출할 때마다 커밋이 발생합니다. 이 시점에서 트랜잭션 관리자는 리소스 관리자를 호출하고 개체에서 이 메서드가 호출 TransactionScope 되었는지 여부에 따라 커밋 또는 롤백하도록 알립니다.

추가 정보

• 트랜잭션 범위를 사용하여 암시적 트랜잭션 구현