High availability with high performance and low and quick maintenance
-
We have SQL ClusterA with 6 Nodes, 3 active and 3 Passive, all passive will be available for any active nodez for Failover. All online database activity will be done on this clusterA, then we have one another SQL ClusterB with 4 nodes, the database on ClusterA will setup merge replication with ClusterB.
My question is:
1- Is Merge replication available on Cluster environment?
2- Is Table Partitioning possible on Cluster environment?
3- All three technologies can be gathered in to give High Performance and High Availability?
We will be doing some data level maintenance and updates (fixing data changes from other database) on ClusterB and also the reports will be served from ClusterB. This will automatically give a Load Balancing environment.
Please help me if this can be achieved or it might has any flaws. We will distribute Database level activity Load among two Clusters via replication and to face large tables we may us benefit from table partitioning. How it would look like?
We have 100000 users online at a time and we have 0 downtime with max. performance is target to achieve. Also the maintenance cost should be considere3e as much we can reduced as possible.
Please give your suggestion and thoughts ...
Shamshad Ali.
------------------------------------------------------------------------------------
-
A few comments:
Why have 3 active and 3 passive nodes? Are you assuming that all 3 active will go down at the same time?
Table partitioning will work with clustering.
Replication will work with clustering.
You won't get 0 downtime as the cluster will cause an outage when it fails over. Mirroring may provide quicker failover as the mirred database is already up and doesn't need recovery.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply