Let\u2019s continue with this third post about SQL Server AlwaysOn and availability groups.<\/p>\n
Others studies are available here:<\/p>\n
This time I\u2019ll talk about read-only secondaries and the new load-balancing support that will be introduced by SQL Server 2016.<\/p>\n
First of all, SQL Server 2014 improved the read-only secondary availability by solving the issue related to secondary accessibility when the primary is offline. However, the redirection to a readable secondary was still basic because it concerned only the first secondary replica defined in the configured priority list. So, unless using a third-party tool it was not possible to use very efficiently all of the resources available from secondaries. Fortunately, the next SQL Server version will change the game by introducing native load-balancing capabilities.<\/p>\n
In order to be able to use this new feature, you must define:<\/p>\n
At this point I admit to expect a GUI for configuring both read-only routes and the routing list rules in a user friendly fashion even if I prefer using T-SQL to be honest. But anyway, let\u2019s try to configure secondary replicas in round-robin fashion as follows:<\/p>\n