I am trying to understand the behavior of failover groups for Azure SQL. It feels like I am missing something obvious.
Imagine the following scenario:
- I have a database with a configured failover group in RegionA and RegionB. RegionA is primary
- I insert row1, update row2 and delete row3 in a table in RegionA
- An outage occurs in RegionA and I end up with table changes above not being replicated to RegionB
- I do a manual, forced failover to RegionB and continue to operate for some time
- RegionA comes back online and the storage in region A is still intact
What happens with row1, row2 and row3 mentioned p.2?
What happens if row2 has been updated while operating in RegionB and now we have 2 conflicting changes?