SQL Server High Availability technologies already gives you a lot of flexibility to fit diverse deployment typologies. Additionally, you can also combine different HA or DR methods to give more granular levels of failover options.
Note: If you buy something from our links, we might earn a commission. See our disclosure statement.
Let us look at some of those techniques, which can help us deploy SQL Server and achieve High Availability goals.
These are Geographically dispersed Clusters and with Storage-level Replication at the storage tier, at the RAW file-system level.
Failover Detection: Automatic or Manual Failover: Automatic or Manual Time to Fail Over : Seconds vs. Minutes Number of Failures it can survive Data Currency / Loss Cost of redundant system(s) Additional hardware and associated costs Additional management and IT Support Granularity of Data Safety: Instance, Database, Table, Row Complexity of implementation Data Consistency How Transparency is the failover process to Clients Privileges Required to Setup Remote DR Site : A-Sync or Sync Impact on Performance
In the next post, I will be talking about SQL Server Availability Groups and its implementation use cases.
Comments are closed.