Post reply

AlwaysOn availability groups & Distributed Transactions

  • February 4, 2014 at 10:20 am

    #283130

    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

  • March 4, 2014 at 9:58 am

    #1693971

    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

  • March 26, 2014 at 4:43 pm

    #1700504

    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

  • March 27, 2014 at 1:06 pm

    #1700856

    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

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply