Long story short, i am in the middle of planning to migrate our databases from a variety of versions to SQL 2014 Always On.A third party has come in and documented what the new infrastructure should look like. In a nutshell, there are 2 hosts in one datacenter, 1 being the primary replica and the second for reporting, and then another one in the other datacenter for failover.Happy days. We have High Availability.Reading the proposal i have questions, and rather than look like a fool with the third party, i would rather look like a fool on here. :-PHopefully someone can answer the below:1. My understanding of the licencing is that Microsoft supplies 1x additional replica for free. If my client wants to save money, then adding an extra replica for reporting isnt going to save him much. Good performance for reports. Correct me if i am wrong on this.2. Secondly, they have specified that there will be 3 networks for the Always On setup.One for the public address. Cool. Thats what the client connect to.One for the heartbeat. Yep thats sweet. Then another one for data synchronisation. Now this one i am baffled on. I cant work out how you would go about setting up a dedicated network for data synchronisation. Or even specifying SQL Server to use this network for data syncs.So what would you normally setup your Always On Clusters with?Heartbeat and public right?
↧