Question: Recently we found out that `.ldf` file of our Microsoft SQL Server 2012 database was growing large. We have set limit as follows: 

[![screenshot](https://i.stack.imgur.com/mKanb.png)](https://i.stack.imgur.com/mKanb.png)

Now we have a question: What will happen when log `.ldf` file reaches its size limit?

Thank you

Answer: 
If the log is full, your database will fail any transaction that requires something written to the log (insert,update,delete, schema change, etc.).

From your screenshot, are you really planning to limit it to 15MB? How big is the database? How big is the largest table in the database? You also mention that it is growing very large. How do you define very large?

Generally speaking, you need your log file to be at least as big as your largest index, so that if you rebuild it, it won't fail. If the log has grown, then that's usually because you need a bigger log file. The only time you'd want to shrink the log file is if you know that a 1 off operation happened that will never happen again (e.g. some sort of data load/export). If your log file is growing significantly larger than your data files, you may want to check your recovery model - if it's full then you need to be taking log backups.
> 
> Now we have a question: what will happen when log .ldf file reaches its size limit?
> 
> 
> 

Let me start by saying that keeping 15mb as log file limit is pure blunder. I never advocate putting limit on transaction log file size, instead ask users to focus on [Better Transaction Log Management](https://www.sqlskills.com/blogs/paul/importance-of-proper-transaction-log-size-management/).

When maximum size of log file restriction is reached log file cannot grow so transactions cannot happen and application would start giving exceptions or would simply fail. This can also lead to database going into recovery state which means users cannot access database at all.