Reference Key Error in Transaction Scope Using Entity Framework - linq

Question

I am Using Transaction Scope for Performing the Insert In Multiple Tables using Try and Catch. But when i am Getting the Error Within Transaction Scope it's not allowing me to Save the Data in catch also.
My Code
using (var transaction = new TransactionScope())
{
try
{
//Insert in Table1
//Insert in Table2
//Insert in Table3
transaction.Complete();
transaction.Dispose();
}
catch(Exception ex)
{
transaction.Dispose();
//Insert in ErrorHandlerTable (Independent Table)
}
}
Now The Problem is whenever i am getting the error in try block for foreign key constraints i am unable to insert into ErrorHandlerTable (Independent Table). Always Getting Following Exception:
{"The INSERT statement conflicted with the FOREIGN KEY constraint \"FK_Table1_PkId\". The conflict occurred in database \"MyTransactionDatabase\", table \"dbo.Table2\", column 'PkId'.\r\nThe statement has been terminated."}
Can anyone help in this?

Answer 1

I think this will help you to revert the operations in the tables, please try using below stuff
using (var transaction = new TransactionScope())
{
try
{
//Insert in Table1
//Insert in Table2
//Insert in Table3
transaction.Complete();
transaction.Dispose();
}
catch(Exception ex)
{
transaction.Dispose();
//what i have changed
context.Table1 Table1Object = new YoSafari.Migration.EntityFramework.Table1(); //Create New Object of the table in which u want to insert i.e. Table1 or Table2 etc..
using (var context = new ContextClass())
{
context.Entry(Table1Object).State = EntityState.Unchanged;
//Insert in ErrorHandlerTable (Independent Table i.e. Table1 or Table2 etc..)
context.SaveChanges();
}
}
}
It will create new object of the tables that will Unchanged the operations and allow you to insert the record in to your ErrorHandlerTable
Please let me know if you are still facing any issue with this.

Answer 2

As answered here INSERT statement conflicted with the FOREIGN KEY constraint :-
In your table ysmgr.Table2, it has a foreign key reference to
another table. The way a FK works is it cannot have a value in that
column that is not also in the primary key column of the referenced
table.
If you have SQL Server Management Studio, open it up and sp_help
'ysmgr.Table2'. See which column that FK is on, and which
column of which table it references. You're inserting some bad data.
So the steps are :-
1.run sp_helpconstraint
2.pay ATTENTION to the constraint_keys column returned for the foreign key

Answer 3

The problem is that, even if your code has disposed the TransactionScope, when it inserts the data in the ErrorHandlerTable tha happens still inside the TransactionScope. So, something is going wrong, and you get a misleading error.
To avoid this, change the code so that the insertion in the ErrorHandlerTable is done outside of the original transaction scope. To do so, you can nest a new using block to provide a new, independent TransactionScope like this:
using(var ts = new TrasanctionScope(TransactionScopeOption.RequiresNew)
or this
using(var ts = new TrasanctionScope(TransactionScopeOption.Suppress)
The first option simply creates a new transaction, indepenend of the original one. But, if your insert is an atomic operation, as it seems, you can also use the second option, which creates a new independent transactionless scope.
In this way you can be sure that your insertion in the ErrorHandlerTable happens without any interference with the original transaction scope.
Please, see this docs:
TransactionScope Constructor (TransactionScopeOption)
TransactionScopeOption Enumeration