I've read countless docs so far about this. What do you guys think about that.
* 2 MS to get HA for them * Initial plan to have both DB's on the same server and have both of them switch in case of any failure using AlwaysOn Availability Group only But that puts all the load on one and not much on the other while everything is fine, so like 99% of the time Can I do this instead: * 2 SQL servers, also with AlwaysOn Availability Group only * One server has the Operational DB, the other the DW * Should one of them fail, the other server takes over just for that DB, hence during the failure there is increased (but acceptable) load. * Once the server is fine again, the primary server is switched back. Doable, making any sense? -R From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Dienstag, 19. August 2014 10:54 To: [email protected] Subject: RE: [msmom] SQL Always on? So basically a two node cluster hosting both databases? From: <mailto:[email protected]> [email protected] [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Andrew Kunz Sent: Dienstag, 19. August 2014 02:54 To: <mailto:[email protected]> [email protected] Subject: RE: [msmom] SQL Always on? I concur We have clusters at main site with truecopy san replication to a DR site and several redundant MS's _____ From: <mailto:[email protected]> [email protected] To: <mailto:[email protected]> [email protected] Subject: RE: [msmom] SQL Always on? Date: Mon, 18 Aug 2014 11:51:02 +0000 Roland, I would suggest a SQL cluster to provide high availability for your SQL DB's. Also, make sure you have a decent SQL backup strategy. We use SQL clustering heavily in our organization for lots of applications. We are currently in the same boat with our SCOM DB's, but we have plans to migrate them to our SQL cluster before too long. From: <mailto:[email protected]> [email protected] [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Roland Janus Sent: Monday, August 18, 2014 7:32 AM To: <mailto:[email protected]> [email protected] Subject: [msmom] SQL Always on? My current design is two Mgt servers for some HA (no network yet) and the Ops and DW DB's on separate servers. But that makes SQL still single point of failure. So should I do Always on for both doubling SQL? Or can I do Always on with just those two, putting a copy of each to the other? OpsDB and DW DB on both? Should one fail, I still have both DB's but the same number of servers? Does that make even sense? :) Is there a point of doing two MgtServers for HA with just one SQL for each DB? -roland
