The transaction log records the operations on the relevant database and also stores information related to database recovery. There are many reasons to shrink the log, some due to insufficient space, and some due to application limitations. The following describes the shrinking operation in simple mode. 1. Command line USE MASTER GO ALTER DATABASE {DBName} SET RECOVERY SIMPLE WITH NO_WAIT GO ALTER DATABASE {DBName} SET RECOVERY SIMPLE --Simple mode GO USE {DBName} GO DBCC SHRINKFILE (N'{DBName}_Log', 8, TRUNCATEONLY) GO USE MASTER GO ALTER DATABASE {DBName} SET RECOVERY FULL WITH NO_WAIT GO ALTER DATABASE {DBName} SET RECOVERY FULL --Restore to full mode 2. Step-by-step operation through the graphical interface 1. Open the database properties window 2. Change the database recovery mode from "full" to "simple" 3. Shrink the database log, "Task" -> "Shrink" 4. After shrinking, change the recovery mode of the database to "full" The above is the full content of this article. I hope it will be helpful for everyone’s study. I also hope that everyone will support 123WORDPRESS.COM. You may also be interested in:
|
<<: Element dynamic routing breadcrumbs implementation example
Related Articles: Website Design for User Experien...
Table of contents Preface call usage accomplish A...
1. Prerequisites We use the require.context metho...
This article introduces how to solve the problem ...
Table of contents The order in which MySQL reads ...
Table of contents 1. Demand 2. Solution 3. The fi...
I logged into the backend to check the solution t...
Table of contents Working principle: What does th...
Table of contents Preface webpack-deb-server webp...
1. Nested routing is also called sub-routing. In ...
//grammar: @media mediatype and | not | only (med...
1. Install dependency packages [root@localhost ~]...
Performance of union all in MySQL 5.6 Part 1:MySQ...
There was an article about the execution process ...
Recently, I encountered many problems when deploy...