Microsoft SQL Server database log truncation

--Reference

Compress log and database file size

/*--Matters needing attention

Follow the steps, do not follow the steps, or you may damage your database.

Generally do not recommend to do 4th, 62 steps.

The 4th step is unsafe, and it is possible to corrupt the database or lose data.

6th step if the log reaches the upper limit, subsequent database processing will fail, and the log will not be restored until it is cleaned.

--*/

--All of the following library names refer to the library name of the database you are working on.

1. Empty log

DUMP TRANSACTION Library name with NO_LOG

2. Truncate the transaction log:

BACKUP LOG Library name with NO_LOG

3. Shrink database files (RU does not compress, database files are not reduced

Enterprise Manager--right--the database you want to compress--all tasks--shrink the database--Shrink the file

--Select Log file--in the shrinkage method to choose to shrink to XXM, here will give a allow to shrink to the minimum m number, directly enter this number, you can determine

--Select the data file--in the contraction way to choose to shrink to XXM, here will give a allow to shrink to the minimum m number, directly enter this number, OK

You can also use SQL statements to complete

--Shrinking the database

DBCC shrinkdatabase (library name)

--Shrink the specified data file, 1 is the file number, you can query through this statement: SELECT * from Sysfiles

DBCC Shrinkfile (1)