December 13, 2012 at 2:40 am
Hi Friends,
I am trying to implement transaction in SSIS for the first time. We are going to migrate few records from source to destination tables using DFT. We are planning to have multiple threads inside the DFT. So if one of the thread fails, the data migration happened thru other threads too should roll back.
I am putting the DFT in a sequence container and setting the transactionoption to required and setting the trasactionoption property of DFTs inside the seq container to supported.
I am getting an error while executing the package. I have started the DTC using Administrative tools. I am still getting the error "The partner transaction manager has disabled its support for remote/network transactions". I saw in few threads that we have to enable remote access thru Component Services.
I am accessing the DB through VPN.
Please help me in resolving the issue.
December 13, 2012 at 6:22 am
MuraliKrishnan1980 (12/13/2012)
Hi Friends,I am trying to implement transaction in SSIS for the first time. We are going to migrate few records from source to destination tables using DFT. We are planning to have multiple threads inside the DFT. So if one of the thread fails, the data migration happened thru other threads too should roll back.
I am putting the DFT in a sequence container and setting the transactionoption to required and setting the trasactionoption property of DFTs inside the seq container to supported.
I am getting an error while executing the package. I have started the DTC using Administrative tools. I am still getting the error "The partner transaction manager has disabled its support for remote/network transactions". I saw in few threads that we have to enable remote access thru Component Services.
I am accessing the DB through VPN.
Please help me in resolving the issue.
I am not completely sure about the issue you are receiving ..
but I hope this link helps..
~ demonfox
___________________________________________________________________
Wondering what I would do next , when I am done with this one :ermm:
December 15, 2012 at 9:18 pm
Hi Guys,
I took a look at the MSDTC article. I have been down that path before during setup.
I guess the question is why use a transaction at all when doing a large ETL jobs.
Here are some ideas that might be quicker overall.
1 - If you can get away with an UPSERT, do it. It is better than trying to roll back a huge load.
It is also restartable. Use a hosptial table to direct errored out rows for research of post processing.
2 - Create a database snapshot before the load. All changed records will go to this sparse file.
When the job errors out, stop the ETL. Use a database restore to put the data back to a steady state.
I ended up rewriting a database warehousing project recently. Plan 1 worked our very well since I did a singe pass of 10 M rows and then did several passes against the hospital table to fix data integrity issues.
In summary, always question why you are going down a path before you start.
Good luck
John Miner
Crafty DBA
www.craftydba.com
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply