150th Blog Post . So, the post involves video demo :)
Previous posts on this series was about using "Geo Replication" to configure active secondary. However, it comes with few limitations like
* No transparent failover capabilities like Always on Listener
* No availability groups and group failover possible
So, Azure Failover Groups provides "Read Only" / "Read Write" connection URLs which allows applications transparent failovers. Read only and Read write workloads get different connection strings and upon failover, applications connect to the appropriate node automatically
Also, one can combine group of databases as a unit of failover and make them failover together as well, as done in Always on availability groups.
Step by step instructions on configuring availability groups provided below
* Configure Primary Server, Secondary Server and Geo Replication as explained in http://strictlysql.blogspot.sg/2017/05/sql-azure-databases-active-secondary.html
* Click on the primary server ( not database ) and select failover groups
* Click on the add group and
Previous posts on this series was about using "Geo Replication" to configure active secondary. However, it comes with few limitations like
* No transparent failover capabilities like Always on Listener
* No availability groups and group failover possible
So, Azure Failover Groups provides "Read Only" / "Read Write" connection URLs which allows applications transparent failovers. Read only and Read write workloads get different connection strings and upon failover, applications connect to the appropriate node automatically
Also, one can combine group of databases as a unit of failover and make them failover together as well, as done in Always on availability groups.
Step by step instructions on configuring availability groups provided below
* Configure Primary Server, Secondary Server and Geo Replication as explained in http://strictlysql.blogspot.sg/2017/05/sql-azure-databases-active-secondary.html
* Click on the primary server ( not database ) and select failover groups
* Click on the add group and
* Provide the failover group a name
* Pick the existing database "db1" to be added to the failover group
* Pick the existing secondary server
* Click on create
* Pick the existing database "db1" to be added to the failover group
* Pick the existing secondary server
* Click on create
* Once done, failover group is listed as shown below
* Click on the failover group, Read only and Read Write URLs can be seen as shown below
* To perform failover click on the failover icon. Post failover, failover group looks like the picture below
To make the understanding easier, I have recorded the video of the demo. Please take a look. Happy learning
5 comments:
We want more article from you because you posting good content on this site. Thankyou.
DOT NET Training in Chennai
DOT NET Course Chennai
dot net institute in chennai
best dotnet training in chennai
DOT NET Training Chennai
Html5 Training in Chennai
QTP Training in Chennai
LoadRunner Training in Chennai
Thanks for posting such useful information. You have done a great job.
MS Azure Training in Hyderabad
oracle sql plsql training
go langaunage training
azure training
java training
salesforce training
hadoop training
Data Science training
linux training
mulesoft training
SAP Secrity online training
oracle sql plsql online training
go langaunage online training
azure online training
java online training
salesforce online training
hadoop online training
Wynn Las Vegas Tickets - JT-Ticket
Buy 여주 출장마사지 tickets 창원 출장마사지 and get free cancellation of your 하남 출장샵 Wynn 대전광역 출장안마 Las Vegas event in Las Vegas on JT-Ticket.com. Free delivery 용인 출장샵 options are available.
Post a Comment