Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Issue with TransactionOption of SSIS Expand / Collapse
Author
Message
Posted Monday, November 5, 2012 10:43 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 12:07 AM
Points: 1,184, Visits: 572
Hi All,

I created a SSIS package which contains two "Execute SQL Tasks" components - one inserts/updates the records in Table1 of DB1 and other inserts/updates the records in Table2 of DB2.

I have also enabled the Transaction by setting the TransactionOption = Required at the package level and TransactionOption = Supported at the component level. So either all operations (done by both EST) or none should commit.

In our dev and test env it is working fine. But on production (with cluster MSDTC), few times it throws an error:
Executing the query "EXEC [etl].[uspRptPopulateFactCourseUsage] @Linked..." failed with the following error: "The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Any suggestions would be useful!!
Post #1381374
Posted Monday, November 5, 2012 11:51 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 6:37 AM
Points: 13,637, Visits: 10,524
Are their problems with the query?
What happens if you run them in SSMS (if possible)? Do they succeed?




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1381397
Posted Tuesday, November 6, 2012 12:04 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 12:07 AM
Points: 1,184, Visits: 572
No issue with the query.
As I mentioned this error doesn't comes very often. 10 in 160 (less than 10%) times this error comes.
Post #1381402
Posted Tuesday, November 6, 2012 12:07 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 6:37 AM
Points: 13,637, Visits: 10,524
Tarun Jaggi (11/6/2012)
No issue with the query.
As I mentioned this error doesn't comes very often. 10 in 160 (less than 10%) times this error comes.


I see you use the parameter mapping if I'm not mistaken. Any possible issues with that? Usually this gives those types of errors.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1381404
Posted Tuesday, November 6, 2012 12:14 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 12:07 AM
Points: 1,184, Visits: 572
As both Execute SQL Tasks are pointing to different databases.
Those Execute SQL Tasks calls stored procedures (that populate the data into the corressponding tables).

Now what I want is lets say if the first Execute SQL Tasks (EST1) completes sucessfully and then the second Execute SQL Tasks (EST2) get failed then all the operations done by EST1 will also get rollbacked. For that I used TransactionProperty of SSIS which worked fine at dev and test env but on Prod (cluster MSDTC) it throws this MSDTC error few times.
Post #1381410
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse