SQL Server database log full solution

Server Error in '/'application. </pre> <pre> -------------------------------------------------------------------------- </pre> <pre>
The log of the database tutorial 'databasename' is full. Back up the transaction logs of the database to release some log space.

If the above error occurs, change the fault recovery mode of the database to "simple" mode.

This problem mainly occurs on websites with large traffic volumes, and log files will increase rapidly.

Solve the problem that SQL database logs are full
1. Right-click database & rarr; attributes & rarr; options & rarr; fault recovery model & rarr; set to simple & rarr; OK;
2. Right-click database & rarr; all tasks & rarr; contract database & rarr; OK;
3. Right-click database & rarr; attribute & rarr; option & rarr; fault recovery model & rarr; set to large-capacity log record & rarr; OK.

1. Clear logs
Dump transaction database name WITH NO_LOG
2. Truncate transaction logs
Backup log database name WITH NO_LOG
3. Compress database files (if not compressed, the database files will not be reduced)
Enterprise Manager -- right-click the database you want to compress -- all tasks -- contract database -- contract file
-- Select Log File -- select to shrink to XXM in the contraction mode. Here, a minimum number of MB allowed to be shrunk is displayed. Enter this number directly and click OK.
-- Select data file -- select to shrink to XXM in the contraction mode. Here, a minimum number of MB allowed to be shrunk is displayed. Enter this number directly and click OK.
You can also use SQL statements to complete
-- Shrink database
Dbcc shrinkdatabase (customer profile)
-- Contract the specified data file. 1 indicates the file number. You can use this statement to query: select * from sysfiles dbcc shrinkfile (1)

In some cases, the transaction log may become very large, resulting in exhausted space or full. Generally, when the transaction log file occupies sufficient disk space and cannot be expanded, you will receive the following error message:
Error: 9002, Severity: 17, State: 2
The log file for database '%. * LS' is full.
In addition to this error message, SQL Server may mark the database as SUSPECT due to the lack of transaction log extended space. For more information about how to recover from this situation, see the "insufficient disk space" topic in SQL Server online help.

In addition, transaction log extensions may cause the following situations:
· Very large transaction log files.
· Transactions may fail and may start to roll back.
· Transactions may take a long time to complete.
· Performance problems may occur.
· Blocking may occur.

Cause
Transaction log extensions may occur for the following reasons or situations:
· Uncommitted transactions
· Very large transactions
· Operation: dbcc dbreindex and CREATE INDEX
· During restoration from transaction log backup
· Client applications do not process all results
· Query times out before the transaction Log is extended. You receive a false "Log Full" error message.
· Unreplicated transactions

Solution
When the log file is full and the SQL database cannot write the file, you can use either of the following methods:
One method: clear logs.
1. Open the query analyzer and enter the command
Dump transaction database name WITH NO_LOG
2. open the Enterprise Manager and right-click the database you want to compress -- all tasks -- shrink database -- shrink file -- select Log File -- select to shrink to XXM in the shrink mode, here we will provide a minimum number of M that can be reduced. Enter this number directly and click OK.