I know that Microsoft has been pretty clear about distributed transactions and cross database transactions not supported in AlwaysOn availability groups and Database Mirroring[url]http://technet.microsoft.com/en-us/library/ms366279.aspx[/url]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
↧