SQL 2019 Enterprise Cluster setup

%3CLINGO-SUB%20id%3D%22lingo-sub-2596527%22%20slang%3D%22en-US%22%3ESQL%202019%20Enterprise%20Cluster%20setup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2596527%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Guys%2C%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20in%20the%20process%20of%20setting%20up%20Always%20on%20HA%20cluster%20on%20SQL%202019%20Enterprise%20on%20virtual%20environment.%3C%2FP%3E%3CP%3ECluster%20will%20include%20SQL%20server%20instance%20on%20two%20separate%20Virtual%20machines%20with%20High%20availability%20groups%20-%20Synchronous%20replication%3C%2FP%3E%3CP%3E-%20Secondary%20-%20%22Readable%20Secondary%20-NO%22%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20help%20me%20clarify%20if%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ea.%20Microsoft%20licensing%20allows%20having%20two%20SQL%20instances%20on%20two%20separate%20VM's%20with%20one%20license%3F%3C%2FP%3E%3CP%3Eb.%20if%20yes%2C%20should%20the%20other%20node%20be%20Read-Only%20%26amp%3B%20Synchronous%20replication%3F%3C%2FP%3E%3CP%3Ec.%20If%20yes%2C%20how%20will%20it%20help%20incase%20of%20DR%20or%20if%20downtime%20is%20required%20on%20Primary%20node%3F%3C%2FP%3E%3CP%3Ed.%20If%20(b)%20is%20no%2C%20and%20both%20nodes%20have%20writable%20copy%20how%20does%20license%20taken%20into%20count%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2596527%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EALways-ON%20High%20availability%20cluster%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESQL%202019%20enterprise%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2597006%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%202019%20Enterprise%20Cluster%20setup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2597006%22%20slang%3D%22en-US%22%3EOnly%20one%20node%20(primary)%20is%20writable.%3CBR%20%2F%3EThe%20secondary%20is%20either%20readable%20or%20not%20readable.%3CBR%20%2F%3EIf%20secondary%20is%20readable%20and%20you%20use%20it%20to%20shift%20some%20load%20from%20primary%20(some%20applications%20use%20ApplicationIntent%3DReadOnly%3B%20in%20connection%20strings)%20-%20you%20need%20the%20second%20license.%3CBR%20%2F%3E%3CBR%20%2F%3EAsynchronous%20%2F%20Synchronous%20affects%20possible%20data%20loss%20during%20failover%3B%20it%20is%20not%20relevant%20to%20licensing.%3CBR%20%2F%3ESynchronous-commit%20mode%20emphasizes%20high%20availability%20over%20performance%2C%20at%20the%20cost%20of%20increased%20transaction%20latency.%20Under%20synchronous-commit%20mode%2C%20transactions%20wait%20to%20send%20the%20transaction%20confirmation%20to%20the%20client%20until%20the%20secondary%20replica%20has%20hardened%20the%20log%20to%20disk.%3C%2FLINGO-BODY%3E
Occasional Visitor

Hey Guys, 

I'm in the process of setting up Always on HA cluster on SQL 2019 Enterprise on virtual environment.

Cluster will include SQL server instance on two separate Virtual machines with High availability groups - Synchronous replication

- Secondary - "Readable Secondary -NO" ?

 

Please help me clarify if;

 

a. Microsoft licensing allows having two SQL instances on two separate VM's with one license?

b. if yes, should the other node be Read-Only & Synchronous replication?

c. If yes, how will it help incase of DR or if downtime is required on Primary node?

d. If (b) is no, and both nodes have writable copy how does license taken into count?

 

thanks

1 Reply
Only one node (primary) is writable.
The secondary is either readable or not readable.
If secondary is readable and you use it to shift some load from primary (some applications use ApplicationIntent=ReadOnly; in connection strings) - you need the second license.

Asynchronous / Synchronous affects possible data loss during failover; it is not relevant to licensing.
Synchronous-commit mode emphasizes high availability over performance, at the cost of increased transaction latency. Under synchronous-commit mode, transactions wait to send the transaction confirmation to the client until the secondary replica has hardened the log to disk.