September 3, 2013 at 12:26 pm
Whenever I have a huge log file for any database with Full as its recovery model
This is what I do to recover disk space...
I change the recovery to simple..then shrink the file and change it back to full.
What exactly is happening here ?
Is this a recommended process?
September 3, 2013 at 12:32 pm
That is not a recommended process, you will have performance issues and you'll be losing all the advantages given by the full recovery model.
Once I found a company where they did that from time to time but never did any log backups (the recommended practice), so my suggestion was to change definitively to the simple recovery model.
Depending on your situation, you should be taking log backups and defining a correct log size or change the recovery model to simple.
Maybe someone will explain with more detail.
September 3, 2013 at 12:58 pm
You're not gaining anything because you need to do a full backup immediately after doing your changes. There used to be a command to "dump tran with no_log" but I'm not sure that works in newer versions. You might be able to dump tran to a nul device but I haven't tried it in a decade.
September 3, 2013 at 1:11 pm
Please take a read through this article on how to manage transaction logs - http://www.sqlservercentral.com/articles/Administration/64582/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 3, 2013 at 1:36 pm
Read Gail's article and then set up log backups to manage your recovery. you can shrink the log file if you need to recover the space, but if you haven't set up management of your files, it will just grow again.
September 5, 2013 at 7:33 am
Take a look at the Autogrowth settings. Default is 10% increase. I change this to a MB increase.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply