Symptoms

I need to reduce K2 log file. From past experience I remember this process.

Even though the below is a SQL command I am performing this on a K2 system database, therefore it is important that you verify. Also we want to preserve historical data, so does the below command affect historical data yes/no]? If not where does the historical data reside?

USE master]
GO
ALTER DATABASEEK2] SET RECOVERY SIMPLE WITH NO_WAIT
GO
USE K2]
GO
DBCC SHRINKFILE ('FG_log_1')
GO
ALTER DATABASE K2 SET RECOVERY FULL
GO
 

Diagnoses

I would like to confirm you that shrinking transaction log per command that you mentioned will not affect "historical/archived" records.

You may also need to consider truncating as well. Please see the following:
Database Truncation:
http://technet.microsoft.com/en-us/library/ms189085(v=sql.105).aspx
* Full Recovery Model: truncation happens during transaction log database backup
* Truncation does not reduce the size of a physical log file. Reducing the physical size of a log file requires shrinking the file. For information about shrinking the size of the physical log file, see Shrinking the Transaction Log

 

Resolution

Customer was able to reduce the size of the log file by running the command mentioned in the ticket details.