ArticlesArticles Most Helpful ArticlesMost Helpful Articles Language SettingsLanguage Settings LoginLogin
RSS Feeds
DrillDown Icon Table of Contents
DrillDown Icon MX
DrillDown Icon MANUALS and Other Info for SQL MANEX Client Server
DrillDown Icon Hardware and Software Requirements for Installing SQL Server
DrillDown Icon List of Modules Converted to MANEX Client Server
DrillDown Icon Installing SQL Server
DrillDown Icon System Administrator
DrillDown Icon Security System
DrillDown Icon Accounting Setup
DrillDown Icon System Setup
DrillDown Icon Operations Manuals
DrillDown Icon System Utilities
DrillDown Icon SQL Server Memory Settings and Performance
DrillDown Icon Definitions
DrillDown Icon How to schedule and automate backups of SQL Server databases in SQL Server Express
DrillDown Icon SQL_FAQ's
DrillDown Icon Verify System License Message
DrillDown Icon Trigger
DrillDown Icon Desktop Time Out
DrillDown Icon Stimulsoft
DrillDown Icon Clear Cycle count-SQL
DrillDown Icon Error Code 0x80004005
DrillDown Icon Error: Update has Failed Database "MANEX" is Full
DrillDown Icon Learn More About Creating SQL Queries from SQL Joins
DrillDown Icon Stop SQL Server Transaction Log (.LDF) files from Growing Indefinitely
DrillDown Icon Version of MSSQL and License Requirement for SQL
DrillDown Icon What Kind of Re-Indexing and Other DB Maintenance will need to be Done?
DrillDown Icon What are the hardware requirements to install SQL Server?
DrillDown Icon Zendesk Ticket
DrillDown Icon Customer Relationship Management (CRM)
DrillDown Icon ManEx Minute
DrillDown Icon ManEx Component Exchange
DrillDown Icon ManEx Supplier Directory & Rankings
  Email This ArticlePrint PreviewPrint Current Article and All Sub-Articles
 
Stop SQL Server Transaction Log (.LDF) files from Growing Indefinitely

 

 

Symptoms

You notice that in your SQL databases directory the .LDF files are growing permanently.

OR 

Users begin experiencing error messages similar to the below.

Solution

Set the recovery mode of your SQL Server databases to 'simple'.

Step-by-step instructions

  1. Perform a full-backup of your SQL Server databases. 
    Note: This is very important since switching from the full or bulk-logged recovery model to the simple recovery model breaks the backup log chain. Therefore, it is strongly recommend to back up the log immediately before switching, which allows you to recover the database up to that point. After switching, you need to take periodic data backups to protect your data and to truncate the inactive portion of the transaction log. [Source]
  2. Switch recovery mode of SQL databases to SIMPLE. 
    (See also: What is simple recovery mode?) 

    Important Note:
  3. "The Simple recovery model lets you restore the database to the point from which it was last backed up. However, this recovery model does not enable you to restore the database to the point of failure or to a particular time."  [Source]


3.    Shrink the transaction log (.LDF) files. 



4.  Perform a full-backup of your SQL Server databases.

Optionally you can use a script for the steps described above:




Another option is to Follow the link below on "How to Prevent the Log File in SQL from Getting to Large" 

 http://www.techrepublic.com/blog/datacenter/help-my-sql-server-log-file-is-too-big/448


Article ID: 5479