Hi,
I have implemented SQL Server Always on Availability Group without windows cluster (WSFC) which is a new feature in 2016 version. Though I have implemented it I have some question about how it works internally.
1. Difference between Synchronous and Asynchronous mode setting separately both in primary and secondary database.
2. How transaction log transfer from primary to secondary? Is it copied by any job or any other way?
3. Snapshot possible? Is it possible to stop the link between primary and secondary and use secondary independently?
4. Long time Secondary down possible? If secondary is down for many days then will primary database keep the transaction log to wait it to be applied in secondary?
5. Login password change possible? If we change login password at primary will the password will replicate in Secondary?
6. Is it beneficial over logshipping?
7. If Primary node is shutdown then will the secondary database still be readable?
8. Is there any query to find transaction gap analysis in Secondary database?
Please note that this is not traditional Always On Availability group with Windows Server Failover Cluster (WSFC). This is Always on Availability Group without any cluster which is commonly call 'Read-Scale Availability group'.
Regards
Arif