Transaction in ADO .NET

Question

5.00/5 (1 vote)

See more:

C#

private void button1_Click(object sender, EventArgs e)
        {
           
            con.Open();
            SqlCommand cmd1 = new SqlCommand();
            SqlCommand cmd2 = new SqlCommand();
            SqlTransaction trn=con.BeginTransaction();
            cmd1.Transaction = trn;
            cmd2.Transaction = trn;
            try
            {
            cmd1.CommandText = "INSERT INTO Table_1 VALUES(64,1)"; //This statment //does not violate the primary key constraint
            cmd1.Connection = con;
            cmd1.ExecuteNonQuery();
            trn.Save("FirstTran"); //Save Point
            cmd2.CommandText = "INSERT INTO Table_1 VALUES(60,1)";//This statment 
// violates the primary key constraint
            cmd2.Connection = con;
            cmd2.ExecuteNonQuery();
             MessageBox.Show("Name of the Connection: "+trn.Connection.ToString());
             MessageBox.Show("Isolation Level of the Transaction: " + trn.IsolationLevel);
             trn.Commit();
            }
            catch (Exception)
            {
                trn.Rollback("FirstTran");
            }
            finally
            {
                con.Close();
            }

        }

I wrote this C# code but the savepoint concept here is not working. The first statement is a valid INSERT statement and second INSERT statement violates the primary key. Hence the cmd2.ExecuteNonQuery() gives an error and control goes inside the CATCH block. According to my knowledge only statment 2 should have been rolled back. But both statments are getting rolled back.
Please Help!!!

Posted 3-Mar-12 23:51pm

puja11191

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Shahin Khorshidnia · Accepted Answer · 2012-03-04T00:08:00

look at the code:

C#

 SqlTransaction trn=con.BeginTransaction(); //It's begining the transaction block

//Transaction Block:

//...

cmd2.ExecuteNonQuery(); // the sequence of the program is breaking here and it's jumping on chatch (.... because of the exception and never be commited.

//...             

trn.Commit();
}
catch (Exception)
{
     trn.Rollback("FirstTran");

//Transaction block end.

}
finally
{
     con.Close();
}

//

Transaction makes an atomic block and all of the code in the Block will be Commited or will be rolled back. That's why both of statments are rolled back.

About the primary key error:

SQL

INSERT INTO Table_1 (Column1, Column2)
                     VALUES(60,1)

If Column2 is not a PK or UK and if you have an ID that is identity(1,1) then you don't have any problem with Primary Key Error.

Check this link please:

http://support.microsoft.com/kb/238163[^]