Hello,
I am trying to understand the capabilities/limitations of geo-replication and Failover groups in Azure with respect to Alwayson AG feature of On premise SQL Sever ENT edition.
In on-premise AG setup, secondary database is not charged if read queries are not offloaded to it and SA (software assurance) agreement is in place. I think we would always be charged for secondary databases of geo-replication or Failover groups - Can you please confirm this?
I know about Azure Hybrid benefits, still we would be charged for secondary databases of geo-replication or Failover groups?
Secondary databases of geo-replication or Failover groups would always be in readable mode, weather we need/use it or not?
I know Failover groups initiate automatic failover after 60 minutes grace period. Is there a way not to wait so long for failover - like when we are notified of some issues in primary, trigger some logic app or something to initiate failover without human intervention?
Does Azure portal or some inbuild mechanism (not DMVs actually) show how much my secondary database is lagging compared to primary ?
Appreciate your insightful response. Thank you.