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 BACKUP LOG <Database_Name> WITH TRUNCATE_ONLY DBCC SHRINKFILE(<Transaction_Log_Name>, 1) GO
After executing the SQL script to truncate transaction log in my SharePoint 2010, it recovered me considerable space now!
Alternatively, You can set the recovery model to "SIMPLE" temporarily, Shrink the Log file and set back to "FULL" recovery model
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 GOImportant: Please note the <database_Name> and <database_log_Name> in above examples are logical names.
Shrink 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)
How about removing the existing Log file and create a new one?
I had SharePoint Content database log file of 30GB! 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
You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.