The first option – backing up the transaction log, should be the first attempt as this will usually solve the problem immediately but in some cases may only gain some time before it occurs again. However, this will give you time to research and implement one of the other options.
How to back up the Transaction Log:
These files should now be shrunk by the following command;
See below for information regarding 'Tasks | Shrink | Files' through the Management Studio, although running the command may be more convenient.
SHRINKFILE translog size WITH NO_INFOMSGS
-- 1st param: Logical name of log file;
-- 2nd param: preferred size (in Mb) to try to shrink log file to
For example, assuming you have 3 transaction log files and you wish to try and shrink (after backing up) the physical files to 5Mb each;
DBCC SHRINKFILE (STARTEAM_log_01, 5) WITH NO_INFOMSGS
DBCC SHRINKFILE (STARTEAM_log_02, 5) WITH NO_INFOMSGS
DBCC SHRINKFILE (STARTEAM_log_03, 5) WITH NO_INFOMSGS
Alternatively, you can attempt to shrink each file through the SQL Server Management Studio as shown below. Ensure the ‘File type’ is ‘Log’, and you have selected ‘Reorganize pages before releasing unused space’. Also enter the requested minimum size to attempt to shrink to.
Please note you may have to repeat this task for each log file listed in the ‘File name’ drop-down.