Availability group planning with MSDTC as a requirement

  • We've got a number of clustered SQL 2008 instances and currently use transactional replication to copy data off to a secondary database to use as a datasource for reporting purposes.

    I'd like to migrate to SQL 2012 and utilize availability groups to point reporting to a read-only secondary replica to eliminate database replication. The application we have requires the use of MSDTC.

    Where I'm kind of running into a brick wall is on what this means for my use of availability groups. Does this mean that I can't use availability groups AT ALL? Or does it just mean that I need to utilize FCI based instances for my availability group members?

    Basically, I want read-only secondary replicas AND MSDTC, am I asking too much? 🙂

Viewing 0 posts

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