How to contract database logs when SQL Server database logs are full

Microsoft ole db provider for SQL Server Error '80040e14'

The log of database 'mis1' is full. Back up the transaction logs of the database to release some log space.

A simple method is used to contract logs:

1. backup log... with no_log
2. shrink the database

OK, synchronization is in progress again ....

Answer:

Check whether the log mode of the database is full? This mode generates a huge amount of logs, which can be changed to the simple mode, and then the database is set to automatically contract.

 

Two Methods for clearing SQL server logs
During usage, we often encounter very large database logs. Here we introduce two solutions ......

Method 1

In general, the contraction of the SQL database does not greatly reduce the size of the database. Its main function is to shrink the log size. This operation should be performed regularly to avoid excessive database logs.

1. Set database mode to simple mode: Open the SQL Enterprise Manager, in the root directory of the console, open Microsoft SQL Server --> SQL Server group --> double-click your server --> double-click to open the database directory --> select your database name (such as the Forum database) forum) --> then right-click and select Properties --> Select Options --> select "simple" in the fault recovery mode, and click OK to save.

2. Right-click the current database to view the shrinking database in all tasks. Generally, the default settings in the database do not need to be adjusted. Click OK directly.

3. After shrinking the database, we recommend that you set your database attributes to the standard mode. The operation method is the same as the first one, because logs are often an important basis for restoring the database in case of exceptions.

 

In sqlserver:

Backup log database name with no_log | truncate_only can intercept transaction logs.

However, after I perform the preceding operations in the database, the transaction log remains unchanged.

The first step is to truncate the non-active transaction logs and not contract the database. Only after the second operation is performed will the database clean up the transaction logs and delete the truncated non-active transactions, and shrink the transaction log file to the appropriate size.
When using SQL Server, the log files in the Database become larger and larger, and you need to delete them. First, I separated the database, right-click the database, and choose "all tasks"> "detach the Database". After the database is detached, I can delete the log file and back up the data. After that, you can add the database to the attached database in all tasks. SQL server will prompt that the log file does not exist and ask if you want to create a new one. Just select YES, in this way, the log file is cleared. This method takes only a few minutes, but in these few minutes, you will not be able to access this database. I think this method is only applicable to small applications. For large systems, you need to find other methods.