January 30, 2014 at 5:11 am
Hello,
Per http://support.microsoft.com/kb/926150, neither distributed transactions or cross-database transactions are supported with database mirroring. There are good reasons for that and I understand where the KB article is coming from.
My question for the community is, with mirroring and availability groups being touted as such a prominent feature of SQL Server for HA, how are you handling the above restriction? Even if you turn off the DTC at the OS layer, there's no way to stop someone from coding a cross-database transaction. Do you just inform your developers that as a consequence of mirroring, you can't insert into two different databases within a transaction? Is there a way to monitor for such an event? Do you just accept the risk, informing the developers that the RPO cannot be zero and there is some risk of transaction loss with mirroring?
It seems on the surface such a basic limitation, but obviously mirroring and AG are used frequently, so how is this limitation being mitigated?
Thank you.
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply