We currently have a SQL Server 2012 environment with FCI based on shared storages, our primary site consists of a two node cluster with one active and one passive, we also have MS DTC installed and running as a clustered resource.
Our current issue is that when we create an "in doubt" transaction on the active node, then shutdown it, the other DB is changed to suspect mode and prevents any client connections. From the MS DTC, we can see one "in doubt" transaction there. Either we abort it or commit it, the instance can start well.
However, we suppose the passive DB can take over the "in doubt" transaction silently and wait for the high level applications to decide whether to commit or rollback it. Is it possible?
Thanks,
Holly