We all know that, if a database is at the Full Recovery model but the transaction log is not being backed up, the transaction log size can grow exponentially.
I know that the remedy for this, in general, is to shrink the database while in Simple Recovery mode, switch to Full Recovery mode, and make sure that maintenance plans are backing up the transaction log at least every hour if possible.
But, prior to running the shrink statement, do you need to back up the transaction log? Or, is this piece optional?
Below are scripts that I tend to run in this situation to backup the transaction log first and then shrink:
BACKUP LOG KLAI to disk = 'C:\SQLServerBackups\Logs\KLAI.BAK'
DBCC SHRINKFILE (2,20)
Again, is that first backup script necessary?