Some of the Transaction Logs and databases grown rapidly and on urgent basis I had to truncate the Log files on SharePoint Content Databases. Here is the SQL script to truncate and shrink SharePoint transaction log:
Use <database_name> GO ALTER DATABASE <database_name> SET RECOVERY SIMPLE GO DBCC SHRINKFILE (Database_Log_Name, 1); GO ALTER DATABASE <database_name> SET RECOVERY FULL GO
Important: Please note the <database_Name> and <database_log_Name> in above examples are logical names.
This sets the recovery model to “SIMPLE” temporarily, Shrink the Log file and set back to “FULL” recovery model. After executing the SQL script to truncate transaction log in my SharePoint 2010, it recovered me considerable space now!
Shrink SharePoint SQL Server Database, Log Files from SSMS:
Shrinking can be done from SQL Server Management Studio also.
Go to SSMS >> Right-click the target Database >> Tasks >> Shrink >> Files (or Database)
Select the File Type and click on “OK” button to start shrinking. Here I’ve selected “Log” File type to shrink SharePoint transaction log files.
Same applies when you want to shrink SharePoint database size. I find it useful when I had to shrink SharePoint search databases.
How about removing the existing Log file and create a new one?
I had a SharePoint Content database log file of 30 GB! So, wanted to remove the existing log and create a new one. Simply add a new log file and remove the existing one from SSMS. Or you can:
- Detach the database
- Rename the log file
- Attach the database without the log file
- Delete the old log file