SQL Azure Databases – Active Secondary – Failover Groups – Part 4

Nagaraj Venkatesan, 2017-10-27

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

Β  Β  Β  Β  Β  * 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
* 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

Original post (opens in new tab)

Rate

β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜…

Share

Share

Rate

β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜…

SQL Azure Databases – Active Secondary – Failover Groups – Part 4

Nagaraj Venkatesan, 2017-10-27

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

          * 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
* 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

Rate

β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜…

Share

Share

Rate

β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜…

Related content

Database Mirroring FAQ: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup?

Question: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? This question was sent to me via email. My reply follows. Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? Databases to be mirrored are currently running on 2005 SQL instances but will be upgraded to 2008 SQL in the near future.

β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜…

Robert Davis

2009-02-23

1,567 reads

Networking – Part 4

You may want to read Part 1 , Part 2 , and Part 3 before continuing. This time around I’d like to talk about social networking. We’ll start with social networking. Facebook, MySpace, and Twitter are all good examples of using technology to let…

β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜…

Andy Warren

2009-02-17

1,530 reads

Speaking at Community Events – More Thoughts

Last week I posted Speaking at Community Events – Time to Raise the Bar?, a first cut at talking about to what degree we should require experience for speakers at events like SQLSaturday as well as when it might be appropriate to add additional focus/limitations on the presentations that are accepted. I’ve got a few more thoughts on the topic this week, and I look forward to your comments.

β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜… β˜…

Andy Warren

2009-02-13

360 reads