we have arund 10 clients whose log file keeps increasing…as of now we are detaching and deleting the log file.But after seeing your comments found that is not the correct way of doing it .
How can i restrict the log file growth.Even in some clients the data file is too large .how to restrict it

Thanks

Good question, the column value of "Nothing" for the log_reuse_wait_desc simply is telling you that there is nothing currently blocking the reuse of the log file. In other words the log has portions available for reuse at that time.

This should mean that as your log file is needed, data can reuse portions that are available. My guess is that you are potentially seeing a lot of activity that is causing the growth to grow beyond the available virtual log files. Perhaps from a long running transaction that you are not seeing at that exact moment you are querying sys.databases.

If you look at the free space of your log file over time, do you notice it ever has plenty of free space available? Remember, the log file will grow as long as needed for the transactions occurring between checkpoints. Once a checkpoint is able to occur, the log file will be truncated (used space will be freed) but it will not be shrunk (the physical file size lowered).

Shrinking is a separate operation and if the file needed to grow to that size once it has as a strong potential of needing to grow to it again at some point so it is best to not shrink but just watch to make sure it doesn’t truly continue to grow out of control.

If that is the case, I would dig deeper and look at just what is occurring on your database, look at if you changed the default recovery interval and look at your overall SQL performance and error logs to ensure nothing else is occurring.

Shoot me an e-mail if you want to chat more or reply in the comments. Either way I am happy to help work through this (not trying to drum up business I am happy to help talk through this on my own time)