The appropriate response to a full transaction log depends partly on what condition or conditions caused the log to fill.To discover what is preventing log truncation in a given case, use the log_reuse_wait and log_reuse_wait_desc columns of the sys.database catalog view.
If space is available on the log disk, you can increase the size of the log file.
The maximum size for log files is two terabytes (TB) per log file.
This topic discusses possible responses to a full transaction log and suggests how to avoid it in the future.
When the transaction log becomes full, SQL Server Database Engine issues a 9002 error.
Your shipment is moving within the UPS network and should be delivered on the scheduled delivery date.
A shipment can remain in this status until it is delivered.
To keep the log from filling up again, take log backups frequently.
To create a transaction log backup You might be able to free disk space on the disk drive that contains the transaction log file for the database by deleting or moving other files.
The freed disk space allows the recovery system to enlarge the log file automatically.
If you cannot free enough disk space on the drive that currently contains the log file, consider moving the file to another drive with sufficient space.
If the log fills during recovery, the Database Engine marks the database as RESOURCE PENDING.