August 28, 2012 at 12:02 am
Comments posted to this topic are about the item AlwaysOn Availability Groups in SQL Server 2012
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 28, 2012 at 5:31 am
Very nicely written. Thanks for sharing 🙂
August 28, 2012 at 6:19 am
Thanks for the feedback, please don't forget to rate the article if you found it useful 🙂
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 28, 2012 at 6:29 am
Perry Whittle (8/28/2012)
Thanks for the feedback, please don't forget to rate the article if you found it useful 🙂
Rated it as 5 stars because that was the limit (it actually deserves more than that:-)).
August 28, 2012 at 7:10 am
Lol you are way to kind, once again thank you.
Btw keep an eye out for my article detailing how to combine failover cluster instances of SQL server with AlwaysOn availability groups, out on 4th Sept
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 28, 2012 at 1:26 pm
Thanks for this article. It may be a while before my company is ready to use AO groups but I will definitely refer to your article when that time comes!
August 28, 2012 at 1:52 pm
Ken Davis (8/28/2012)
Thanks for this article. It may be a while before my company is ready to use AO groups but I will definitely refer to your article when that time comes!
Thanks for the feedback, please don't forget to rate the article if you found it useful 🙂
Also feel free to add it to your SSC briefcase 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 29, 2012 at 10:44 pm
Very nice!
August 29, 2012 at 11:45 pm
DanOrc (8/29/2012)
Very nice!
Thank you very much for your kind feedback, please don't forget to rate the article if you found it useful.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 3, 2012 at 2:52 pm
Hi,
Have you guys experience where when you failover the AG, the clients do not pickup the new IP address and so cannot connect.
See related link:
http://social.msdn.microsoft.com/Forums/en-US/sqlhadr/thread/34e100db-a340-429d-b42a-41cdd8d4e09b
This decribes what is basically happening to us. We've setup a TEST environment to check out the AG stuff and this is the biggest problem we're having so far. I'm unable to find a bug number or anything on MS website.
TIA
Steve
March 5, 2013 at 1:25 pm
Nice article Perry, very informative. Maybe you can help me with a question I have. I'm looking for a way (in a DMV) to see how far the secondary replica has fallen behind under heavy database load (inserts, updates, deletes) on the primary. In other words, is there a way to see how many transactions the secondary needs to apply so it is caught up and in sync with the primary?
Also, is there an easy way to measure the overhead cost of using sync compared to async?
August 8, 2013 at 7:35 am
How many availability groups can you have on the Primary server?
In the real world, you may have one or more associated databases that would be required to fail over as a group but that doesn't mean adding all the databases to the one group and failing them all. This is where I get a bit confused. So, can you have more than one group, on the one server, on the one WSFC node?
I am designing a possible SQL 2012 HA & DR within an WSFC and am worried about the above questions...see attachment for architecture
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply