• NJ-DBA - Monday, December 11, 2017 7:01 AM

    Do I really get to correct Steve Jones?  Nah, I must be wrong.... SQL Server 2017 doesnt strictly require WSFC for AlwaysOn AGs.  For example, on Linux there is no WSFC but AGs work fine using the "EXTERNAL" option in the wizard.  I must confess that I've not set it up without a cluster, but I bet it would work.  This guy is doing it:  http://sqlha.com/2017/02/22/alwayson-availability-groups-no-underlying-cluster-sql-server-v-next/  here is another approach:  http://www.sqlmastersconsulting.com.au/SQL-Server-Blog/sql-server-2017-read-scale-out-availability-group

    MS documentation:  https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/read-scale-availability-groups

    In any event, I dont think you are getting automatic failover without the cluster though.

    You do, and that's cool. Didn't realize that was working. I thought there was still a WSFC involved.

    I'll have to give that a try, though I know Allan has had issues with some of the newer AG stuff as it's been released. There must be something else with the OP that missed earlier in the steps. I'll confess I haven't tried this, but perhaps this is something I need to do in Jan when I'm back in the office.