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

Transactions in SQL Server 2005 Integration Services Expand / Collapse
Author
Message
Posted Wednesday, December 29, 2004 10:15 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Sunday, November 10, 2013 11:52 AM
Points: 877, Visits: 188
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/jthomson/transactionsinsqlserver2005integrationservices.asp



Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
Post #152959
Posted Tuesday, January 4, 2005 9:28 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Saturday, March 14, 2009 7:23 AM
Points: 12, Visits: 6
This would also by inference mean that there is no such thing as nested transactions? Or is there another mechanism that could be employed for that?
Post #153512
Posted Wednesday, January 5, 2005 2:18 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Sunday, November 10, 2013 11:52 AM
Points: 877, Visits: 188

Good question, and coincidentally one that I was asked yesterday by a colleague upon reading the article.

You are correct, nested transactions are not supported. This would be an interesting feature request for future versions althought I would fear that this would impact the inherent simplicity of the current behaviour.

Perhaps this could be handled via a new setting for TransactionOption, 'SupportedNested' or something similar.

Regards



Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
Post #153672
Posted Wednesday, May 31, 2006 11:59 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, October 25, 2010 5:53 AM
Points: 1, Visits: 4

Hi,

I am having some problem with SSIS transaction. Eventhought I tried to imitate the concept that Jamie presented. My workflow is as followed

*********************************

For Each ADO.Record in Oracle (transaction=not supported)

If (Certain_Field_Value = 'A')

Lookup Data in SQL DB with values from Oracle (transaction=not supported)

DO Sequence A (Start a Transaction , transaction=required)

INSERT/UPDATE some records in SQLDB(transaction=supported)

Finish Sequence A ( transaction should stop here)

UPDATE Oracle DB ( Execute SQLTask, transaction=not supported)

If (Certain_Field_Value = 'B')

Lookup Data in SQL DB with values from Oracle (transaction=not supported)

DO Sequence B (Start a Transaction , transaction = required)

INSERT/UPDATE some records in SQLDB (transaction=supported)

Finish Sequence A ( transaction should stop here)

UPDATE Oracle DB ( Execute SQLTask, transaction=not supported)

If (Certain_Field_Value = 'C')

------------

------------

End ForEach Loop

*************************************

My requirements are that I want separate transaction for each Sequence A, B, C, etc... If Sequence A transaction fails, the other should still be continuing with another transaction.

But I am getting an error regarding the OLEDB Error in next Task (e.g in Certain_Field_Value = 'B') "Lookup Data in SQL DB with values from Oracle ", the error message is  ".......Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction. ".

What is it the I am doing wrong?

Regards

KyawAM

Post #284115
Posted Friday, February 2, 2007 2:04 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 5:51 AM
Points: 6,266, Visits: 2,028
Nested transactions are complex and "dangerous". There is a raw limit of 32 on the maximum nested level (on both SQL Server 2000 and 2005) which you can hit if you are not careful. Triggers complicate this things further and therefore the logic on the client code gets really convoluted.

I beleive those reasons should be enough for keeping you from getting into the nested transactions world. I have been there and it is really ugly. Most non trivial applications employ the single transaction model for speed and clarity.

Good Luck,




* Noel
Post #342196
Posted Friday, February 2, 2007 2:10 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Sunday, November 10, 2013 11:52 AM
Points: 877, Visits: 188

Hi there Noel,

In this case the transactions are handled by DTC. Does the same still aply?

-Jamie

 



Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
Post #342197
Posted Monday, May 5, 2008 1:03 PM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Friday, July 6, 2012 9:12 AM
Points: 500, Visits: 183
Jamie, thanks for adding "In this case the transactions are handled by DTC."
I've been trying to find out what kind of trans. the Sequence Container used.

We've had issues with DTC in the past.

If need be, is there a way to use SQL Transactions with the Sequence Container?

much appreciated! - John


Skål - jh
Post #495198
Posted Monday, October 20, 2008 10:06 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, September 26, 2013 10:41 AM
Points: 9, Visits: 22
I am thinking that SSIS DTC does not really work or that there are some special attributes
that tasks contained in a sequence with transaction=required, that these tasks need to
have. Is sequentiality and same-thread guaranteed for all tasks in a sequence? I'm getting
failures on the first task in a transactioned sequence for no reason, am tempted to bag
SSIS/DTC and go with the literal BEGIN TRANSACTION ( which would involve redesigning
the whole loop -- arrgghh )
Post #588671
Posted Monday, October 20, 2008 2:36 PM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Friday, July 6, 2012 9:12 AM
Points: 500, Visits: 183
Since this issue, in other packages I've built,
I have found that if in the same package,
there is a truncate task of the same table I am loading
then DTC will lock up, but SQL transactions will not.

If that is your situation, you might try putting the truncate in a separate package all together and then use a master controller package to control the flow from truncate to loading packages.

But I have had DTC hang on that server even without the truncate task and have been tending to avoid it.

hth


Skål - jh
Post #588815
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse