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

AlwaysOn availability groups & Distributed Transactions Expand / Collapse
Author
Message
Posted Tuesday, February 4, 2014 10:20 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, December 4, 2014 10:02 AM
Points: 30, Visits: 481
I know that Microsoft has been pretty clear about distributed transactions and cross database transactions not supported in AlwaysOn availability groups and Database Mirroring

http://technet.microsoft.com/en-us/library/ms366279.aspx

I'm just interested to find out from anyone who already has AlwaysOn availability setup and may've tried this before, is this a hard restriction that distributed transactions/cross database transactions will outright fail with error message saying you can't run distributed transactions because the database is participating in AlwaysOn availability group, or is it a soft restriction which distributed transactions will succeed under normal scenarios but you're not guaranteed transactional consistency in case of failover?

I'm still evaluating whether it's feasible to leverage AlwaysOn to create secondary copies of our data warehouse reporting database, but we do leverage distributed transactions for incremental loading to ensure data consistency between our staging and reporting server and would require additional dev work to do this without leveraging distributed transactions
Post #1537853
Posted Tuesday, March 4, 2014 9:58 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, November 21, 2014 11:24 AM
Points: 153, Visits: 981
To my knowledge and experience you can run a
BEGIN DISTRIBUTED TRANSACTION

very well.


Andreas

---------------------------------------------------
MVP SQL Server
Microsoft Certified Master SQL Server 2008
Microsoft Certified Solutions Master Data Platform, SQL Server 2012
www.insidesql.org/blogs/andreaswolter
www.andreas-wolter.com
Post #1547424
Posted Wednesday, March 26, 2014 4:43 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, December 4, 2014 10:02 AM
Points: 30, Visits: 481
thanks, so this sounds like a soft restriction rather than hard restriction based on your experience. doesn't mean i want to do something not officially supported by MS but at least it gives us an option

Post #1555211
Posted Thursday, March 27, 2014 1:06 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 9:57 AM
Points: 1,194, Visits: 2,234
irabufan (3/26/2014)
thanks, so this sounds like a soft restriction rather than hard restriction based on your experience. doesn't mean i want to do something not officially supported by MS but at least it gives us an option


It's a soft restriction but not supported by MS due to the integrity issues during the failover.

Check this ..

http://msdn.microsoft.com/en-us/library/ms366279.aspx

--
SQLBuddy
Post #1555619
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse