Solved

Set recovery model to full.  What to do with existing log (.ldf) files?

Posted on 2016-09-08
5
72 Views
Last Modified: 2016-09-08
A consultant changed the recovery model from full to simple for our production SQL databases.  I would like to set the recovery model back to full.  However, the log files (.ldf) have a date/time which is the same as the .mdf files.  I'm not sure what to do with the log files.  Should I delete them or leave them alone?  I wonder why the log files have the same date/time as the the .mdf files if the recovery model is set to simple?  Thank you.Screenshot of date/time for mdf and ldf files
0
Comment
Question by:davidrobertbristow
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 69

Expert Comment

by:Scott Pletcher
ID: 41790081
DON'T EVER DELETE LOG FILES!

Log files are still needed, even in simple mode.
0
 
LVL 69

Accepted Solution

by:
Scott Pletcher earned 500 total points
ID: 41790084
Instead, simply change the mode back to FULL and take a full database backup as soon as you can.  Then start taking regular log backups again, as you would any time a db is in FULL recovery model.  That's all you need to do, nothing extra/special.
0
 

Author Comment

by:davidrobertbristow
ID: 41790090
Can I change the recovery model back to full during production or does it need to be done off-hours?
0
 
LVL 69

Expert Comment

by:Scott Pletcher
ID: 41790110
You can do it any time.  

But it won't actually provide any additional recovery possibilities until you've taken a full db backup.  That is, the point of full recovery mode is to allow you to recover changes lost if the db fails; the log file is used "forward recover" (as it's called), i.e. reapply data, to the db.  

But you can't use the log to forward recover until you have a full db backup from which to work.  And a full backup made when in SIMPLE recovery mode won't work.  You have to have a full backup made after the db was put back into full mode to use as a valid starting recovery point.
0
 

Author Comment

by:davidrobertbristow
ID: 41790114
I understand.  Set the recovery mode to full.  Then, take a full DB backup to start the log file chain.  Thank you!
0

Featured Post

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
What if you have to shut down the entire Citrix infrastructure for hardware maintenance, software upgrades or "the unknown"? I developed this plan for "the unknown" and hope that it helps you as well. This article explains how to properly shut down …
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.

630 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question