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
JSON (JavaScript Object Notation, JS Object Notat...
But recently I found that using this method will c...
Sometimes the theme of a project cannot satisfy e...
MySQL installation (4, 5, 6 can be omitted) State...
<br />Forms are an important channel for use...
MySQL full text search Chinese solution Recently,...
Create a Directory cd /usr/local/docker/ mkdir je...
Think big and small, then redirect. Sometimes Lin...
This article summarizes the principles and usage ...
MyISAM storage engine MyISAM is based on the ISAM...
Table of contents Preface 🍹Preparation 🍲vue3 usag...
Detailed explanation of the usage of DECIMAL in M...
Table of contents 1. Scope 1. Global scope 2. Loc...
In the front-end and back-end separation developm...
Sometimes you may encounter a situation where a S...