Home > database >  Limit is essentially log size
Limit is essentially log size

Time:05-06

Using Java long connection sqlserver2012r2 database, the log file for a period of time is a few hundred G size, smaller contraction after using a simple model database log files, but after a period of time and restore to hundreds of G, the log file limit of 2 G, the database will prompt "the transaction log is full, the reason is: log_backup",
What a great god:
1) simple pattern shrinking database log data will be lost?
2) have what method can control the size of the database log?
3) complete mode, automatic shrink database, don't work is there any way to solve?

CodePudding user response:

1) simple pattern shrinking database log data will be lost?
- & gt; Possible.

2) have what method can control the size of the database log?
- & gt; A complete pattern, regularly (every 30 minutes, for example) for log backups.

3) complete mode, automatic shrink database, don't work is there any way to solve?
- & gt; A complete pattern, regularly (every 30 minutes, for example) for log backups.
  • Related