InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comMon, 20 May 2013 23:14:04 GMT20http://www.sqlservercentral.com/Forums/Topic1384077-1550-1.aspxMost likely full recovery model and no log backups. See the first article that Anthony posted.One other point, a large log will no cause poor performance. Shrinking a log will not improve performance.Thu, 15 Nov 2012 04:05:25 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1384077-1550-1.aspx[quote][b]miazaidi (11/15/2012)[/b][hr]User would have performed large DML operation, DELETE or UPDATEShrink you database, it will reduce the size of your .ldf as well as .mdfUSE [DATABASE NAME]GODBCC SHRINKDATABASE(N'DATABASE NAME' )GO[/quote]No, don't do that. It'll fragment the indexes, cause performance problems and probably won't solve the large log problemThu, 15 Nov 2012 04:03:34 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1384077-1550-1.aspx[quote][b]miazaidi (11/15/2012)[/b][hr]User would have performed large DML operation, DELETE or UPDATEShrink you database, it will reduce the size of your .ldf as well as .mdfUSE [DATABASE NAME]GODBCC SHRINKDATABASE(N'DATABASE NAME' )GO[/quote]Why shrink database when the OP said it was the log?Also you do know the implications of shrinking a database?Thu, 15 Nov 2012 03:17:51 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1384077-1550-1.aspxUser would have performed large DML operation, DELETE or UPDATEShrink you database, it will reduce the size of your .ldf as well as .mdfUSE [DATABASE NAME]GODBCC SHRINKDATABASE(N'DATABASE NAME' )GOThu, 15 Nov 2012 03:15:50 GMTmiazaidihttp://www.sqlservercentral.com/Forums/Topic1384077-1550-1.aspxManaging Transaction Logs - [url]http://www.sqlservercentral.com/articles/Administration/64582/[/url]Why is my transaction Log full - [url]http://www.sqlservercentral.com/articles/Transaction+Logs/72488/[/url]Stairway to Transaction Log management - [url]http://www.sqlservercentral.com/stairway/73776/[/url]Recovery Models - [url]http://msdn.microsoft.com/en-us/library/ms189275.aspx[/url]Accidental DBA Guide - Chapter 8 - [url]http://www.sqlservercentral.com/articles/books/76296/[/url]SQL Server Backup & Restore - [url]http://www.sqlservercentral.com/articles/books/89519/[/url]Comming SoonSQL Server Transaction Log Management - [url]http://www.sqlservercentral.com/articles/books/94938/[/url]Tue, 13 Nov 2012 07:34:46 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1384077-1550-1.aspxWhat you need to ensure is that you have a suitable back-up policy in place.If the Database is in Full recovery then you need to ensure that you run regular transaction log backups and a daily full backup.If in simple recovery then you shall need to ensure that you run a full backup at least daily depending on your RPO and RTO.can you confirm what recovery model is being used by the database?If it is in full recovery ensure that a full backup has been taken and then run a transaction log backup. After this you may be able to run DBCC Shrinkfile against the DB Log file Tue, 13 Nov 2012 07:26:49 GMThs24http://www.sqlservercentral.com/Forums/Topic1384077-1550-1.aspxI have discovered yesterday that the size of the log file on my database has increased to 55 Gb while the datafile is 8 Gb. The users are complaining that applications using this database are very slow. The server is sql server 2008 R2.What can i quickly do to reduce the size of the log file? The free space disk on my server is 35 MB!Thanks in advance.Tue, 13 Nov 2012 07:16:56 GMTabdielmomo