Solved

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

Posted on 2016-09-08
5
47 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
  • 3
  • 2
5 Comments
 
LVL 69

Expert Comment

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

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

Accepted Solution

by:
ScottPletcher 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:ScottPletcher
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

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

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

I have a large data set and a SSIS package. How can I load this file in multi threading?
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
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.

911 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

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now