We need to arrange a second occasion/server of SQL Server such that each situations can be saved in sync. The reason being we have to separate some customers and processes out to a separate server for enterprise causes.
Extra data (requested in feedback):
- Neither occasion could be read-only
- It doesn’t have to be synced in realtime, however that may be good
- We’ve full management of the desk schemas
We have performed numerous analysis, however most potential choices are a part of catastrophe restoration options, so we’re unsure if these are proper for this.
I am unsure learn how to whittle down this checklist with out really attempting the totally different choices, however that may be very time consuming. If there’s an choice I am lacking, that may be very useful.
All the time On Availability Teams
Home windows Server Failover Clustering with SQL Server (Is that this what is often meant by clustering?)