Standard Availability Groups

Question

Post reply

Standard Availability Groups

Steve Jones - SSC Editor

SSC Guru

Points: 736172
More actions
December 15, 2016 at 8:43 pm

#324058

Comments posted to this topic are about the item Standard Availability Groups
December 19, 2016 at 12:24 am

This was removed by the editor as SPAM

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

George Vobr SSCrazy Eights Points: 9996 More actions · Answer 1

Simple, but interesting question, thanks Steve. But I shot on Google today too hastily and missed. It was necessary

to start shooting from the MSDN https://msdn.microsoft.com/en-us/library/cc645993.aspx ... :crying:

Ed Wagner SSC Guru Points: 287026 More actions · Answer 2

George Vobr (12/16/2016)
Simple, but interesting question, thanks Steve. But I shot on Google today too hastily and missed. It was necessary
to start shooting from the MSDN https://msdn.microsoft.com/en-us/library/cc645993.aspx ... :crying:

I found the same document and also got it wrong.

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

tom.w.brannon Hall of Fame Points: 3976 More actions · Answer 3

I checked https://msdn.microsoft.com/en-us/library/ff878487.aspx#RestrictionsAG and found the paragraph

Maximum number of availability groups and availability databases per computer: The actual number of databases and availability groups you can put on a computer (VM or physical) depends on the hardware and workload, but there is no enforced limit. Microsoft has extensively tested with 10 AGs and 100 DBs per physical machine. Signs of overloaded systems can include, but are not limited to, worker thread exhaustion, slow response times for availability group system views and DMVs, and/or stalled dispatcher system dumps. Please make sure to thoroughly test your environment with a production-like workload to ensure it can handle peak workload capacity within your application SLAs. When considering SLAs be sure to consider load under failure conditions as well as expected response times.

The bolding is mine. No mention of changing by edition.

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 4

Standard Edition AGs have always had a maximum of 1 db per AG. A bit like mirroring with extras.

BillLudlow SSCertifiable Points: 6553 More actions · Answer 5

BillLudlow

SSCertifiable

Points: 6553

December 16, 2016 at 7:21 am

#1918390

I made the same interpretation

:o(

Revenant SSC-Forever Points: 42467 More actions · Answer 6

https://www.microsoft.com/en-us/sql-server/sql-server-editions says 2.

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 7

Revenant (12/16/2016)
https://www.microsoft.com/en-us/sql-server/sql-server-editions says 2.

Two NODE, single database failover.

Revenant SSC-Forever Points: 42467 More actions · Answer 8

Beatrix Kiddo (12/16/2016)
Revenant (12/16/2016)
https://www.microsoft.com/en-us/sql-server/sql-server-editions says 2.
Two NODE, single database failover.

I will have to work on my reading. Thanks, Bea!

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 9

Hah, I got one right, and the power went to my head :-D.

TomThomson SSC Guru Points: 104773 More actions · Answer 10

I got it wrong, because i thought that when a lost of the Standard Edition restrictions were discarded in SP1 the only ones remaining were to do with performance and capacity limits, not to do with things like reliability and availability.

Tom