Shulou(Shulou.com)06/01 Report--

Preface

Recently experienced a server SQL SERVER database server-side transaction log full, resulting in the server database can not write data into the downtime event, after the occurrence of this event, I would like to advise colleagues, if there is no absolute sufficient storage space, database transaction log files must not take a full backup, the amount of data backed up is you can not bear, a simple backup The following is the operation of shrinking the database transaction log, hoping to help you!

Database transaction log shrinkage is performed through the graphical interface as follows:

Step 1: right-click the database properties

Step 2: change the database recovery model from "complete" to "simple"

Step 3: right-click the database, "Task"-> "shrink"-> "File"

Step 4: shrink the database log, select the file type "log", and shrink the file to the minimum size within the shrink operation

Note: if the disk space is full, you can not shrink the database transaction log files, you can first separate part of the unused database, and then copy the MDF file and LDF file to other spare disks to free disk space. After the log shrinks, the separated database files will be attached again.

To detach the database operation, right-click and select "Task"-> "detach" as shown below:

Summary

The above is the whole content of this article. I hope the content of this article has a certain reference and learning value for everyone's study or work. Thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.