Skip to main content
Tweeted twitter.com/StackDBAs/status/1039393694493753344
added correct link
Source Link
user158823
user158823

Is there a reason to have Regular SQL Failover Clustering when database is in Azure Cloud?

I understand the benefits having Availability Groups in Azure Cloud for Database-Level protection. People can transition heavy Read queries to the secondary replica (to prevent locking-blocking, tempdb issues), offload maintenance tasks, etc.

However why would someone require Failover Clustering in Azure Cloud for Server-level protection? Don't Cloud Services inherently offer server level protection by itself? This is different to question which asks about Availability Groups: Azure Failover Clustering vs On Premise Failover ClusteringAny Reason to have AlwaysOn Failover Clustering in Azure Cloud? , this question is about FCI

Is there a reason to have Regular SQL Failover Clustering when database is in Azure Cloud?

I understand the benefits having Availability Groups in Azure Cloud for Database-Level protection. People can transition heavy Read queries to the secondary replica (to prevent locking-blocking, tempdb issues), offload maintenance tasks, etc.

However why would someone require Failover Clustering in Azure Cloud for Server-level protection? Don't Cloud Services inherently offer server level protection by itself? This is different to question which asks about Availability Groups: Azure Failover Clustering vs On Premise Failover Clustering

Is there a reason to have Regular SQL Failover Clustering when database is in Azure Cloud?

I understand the benefits having Availability Groups in Azure Cloud for Database-Level protection. People can transition heavy Read queries to the secondary replica (to prevent locking-blocking, tempdb issues), offload maintenance tasks, etc.

However why would someone require Failover Clustering in Azure Cloud for Server-level protection? Don't Cloud Services inherently offer server level protection by itself? This is different to question which asks about Availability Groups: Any Reason to have AlwaysOn Failover Clustering in Azure Cloud? , this question is about FCI

edited tags
Source Link
user158823
user158823

Is there a reason to have Regular SQL Failover Clustering when database is in Azure Cloud?

I understand the benefits having Availability Groups in Azure Cloud for Database-Level protection. People can transition heavy Read queries to the secondary replica (to prevent locking-blocking, tempdb issues), offload maintenance tasks, etc.

However why would someone require Failover Clustering in Azure Cloud for Server-level protection? Don't Cloud Services inherently offer server level protection by itself? SimilarThis is different to question which asks about Availability Groups: Azure Failover Clustering vs On Premise Failover Clustering

Is there a reason to have Regular SQL Failover Clustering when database is in Azure Cloud?

I understand the benefits having Availability Groups in Azure Cloud for Database-Level protection. People can transition heavy Read queries to the secondary replica (to prevent locking-blocking, tempdb issues), offload maintenance tasks, etc.

However why would someone require Failover Clustering in Azure Cloud for Server-level protection? Don't Cloud Services inherently offer server level protection by itself? Similar to question which asks about Availability Groups: Azure Failover Clustering vs On Premise Failover Clustering

Is there a reason to have Regular SQL Failover Clustering when database is in Azure Cloud?

I understand the benefits having Availability Groups in Azure Cloud for Database-Level protection. People can transition heavy Read queries to the secondary replica (to prevent locking-blocking, tempdb issues), offload maintenance tasks, etc.

However why would someone require Failover Clustering in Azure Cloud for Server-level protection? Don't Cloud Services inherently offer server level protection by itself? This is different to question which asks about Availability Groups: Azure Failover Clustering vs On Premise Failover Clustering

Source Link
user158823
user158823

Any Reason to have Regular Failover Clustering in Azure Cloud?

Is there a reason to have Regular SQL Failover Clustering when database is in Azure Cloud?

I understand the benefits having Availability Groups in Azure Cloud for Database-Level protection. People can transition heavy Read queries to the secondary replica (to prevent locking-blocking, tempdb issues), offload maintenance tasks, etc.

However why would someone require Failover Clustering in Azure Cloud for Server-level protection? Don't Cloud Services inherently offer server level protection by itself? Similar to question which asks about Availability Groups: Azure Failover Clustering vs On Premise Failover Clustering