: MSSQL database scale is very big, there are about 1000 g, database has done image>, because a lot of writing and delete operations, resulting in: the transaction log is full the error message, and then led to the suspension of service can't write,
Question 1: the log is set to the percentage growth and unlimited, why the transaction log is full of mistakes, rather than automatically growth?
Question 2: how in the case of mirror synchronization solution this log is full of problems? (best can keep image synchronization)
Question 3: how can the avoid the happening of this kind of situation?
Operation platform: Microsoft Windows NT 6.2 (9200)
Products: Microsoft SQL Server Enterprise (64 - bit)
Version: 11.0.2100.60