Database log files not shrinking

Then shrink log file. You will see the disk really free up it's storage. Don't forget to modify database recovery mode back to Full. I hope it can help you well. Good luck! We are running production database having 2 logfiles.

Recovery model is set to simple but i am unable to shrink logfile as i have tried many times but no success. Can you please help me out to get over this issue without making any impact on database as well as user degradation. Your quick response will be highly appreciated. You must be logged in to reply to this topic. Login to reply. October 22, at am Restarting a server instance resizes the transaction log of the tempdb database to its original, pre-autogrow size.

This can reduce the performance of the tempdb transaction log. You can avoid this overhead by increasing the size of the tempdb transaction log after starting or restarting the server instance. For more information, see tempdb Database. Note the following:. The file growth increment on a log file should be sufficiently large to avoid frequent expansion.

A good pointer to properly size a transaction log is monitoring the amount of log occupied during:. A small growth increment can generate too many small VLFs and can reduce performance. To determine the optimal VLF distribution for the current transaction log size of all databases in a given instance, and the required growth increments to achieve the required size, see this script.

A large growth increment can generate too few and large VLFs and can also affect performance. Even with autogrow enabled, you can receive a message that the transaction log is full, if it cannot grow fast enough to satisfy the needs of your query. Or it could be an indication of a problem with replication such as resource contention.

Check this page for more info. To continue this discussion, please ask a new question. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need.

Learn More ». Get answers from your peers along with millions of IT pros who visit Spiceworks. Primary node, one secondary node in Sync mode and another secondary node in Async mode. Are you running the command in the context of the correct database? I have double verified , Yes correct database.

What is the state of the Database read only; restoring etc? Please click "Mark As Answer" if my post helped. Tony C. Hi Dan, Tried as you suggested but getting below same error. Can you locate the Transaction Log in Windows Explorer?

That's not what I asked Hi Anthony, Yes, able to view log file through windows explorer. Ok, try and rename the file; if it is locked into SQL Server the renaming will fail.

Hi Anthony , I Did the same , the log file is accessing. What is your opinion on it. Detach the Database. For this we have required client approval , it is a production server.

I will wait other any suggestions from forum guys. Hi All, After multiple research , we have resolved the issue by using below query got exact filename for shrink the log file. Thank you all for quick responses.

Can you backup the log and then shrink the database? Hi Sequel, The database is not configured any type of replication.