- Description of the situation: We installed 2 "Microsoft SQL Server" instances (version 2016 [13.0.5698.0] Enterprise edition) and 1 Availability Group (For example with names: NAVDB02, NAVDB03 and AO1). And after some weeks some colleague turned off whole server where is Secondary replica (he didn’t notice that there is "Microsoft SQL Server" running in AoAG configuration). In this situation Primary replica keep data for synchronization with Secondary in transaction log. If Secondary replica is down for a longer time, then transaction log grows and grows.
- Question: What happens when the transaction log is on 100%full? (I wasn’t able to test it, because it occurred in our production environment).
P.S.
O.S. is Microsoft Windows Server [Version 10.0.14393] (2016, Datacenter edition)
__________________________________________________________ If isn't above described anything, the following applies: Technical details: * OS: Windows Server v2016, English, Enterprise Edition, x64, SP1 ** My User-Account is member of 'Administrators' local security group. * MS-SQL-Server: v2016, English, Enterprise Edition, x64, SP2 ** My User-Account is member of 'SysAdmin' db-role.