November 14, 2018 at 8:08 pm
Comments posted to this topic are about the item Building an AG
November 14, 2018 at 11:15 pm
Nice question, thanks, Steve
Have been revisiting HA for my new contract, so this one was easy
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
November 15, 2018 at 3:10 am
But this is not true for Basic Availability Groups, isn't it?
https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/basic-availability-groups-always-on-availability-groups?view=sql-server-2016
An Always On basic availability group can be created on any two SQL Server 2016 Standard Edition servers. When you create a basic availability group, you must specify both replicas during creation.
Have a nice day,Christoph
November 15, 2018 at 4:07 am
nice questions steve,
ta
---------------------------------------------------------------------------------------
The more you know, the more you know that you dont know
November 15, 2018 at 5:01 am
Hi Christoph,
as far as I know it does apply to Basic Availability groups, the limitations are different there it's more along the line of two nodes and only one DB per bAG (Basic Availability Group). WSFC is still a requirement
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply