Symptoms

Assume that you run an instance of Microsoft SQL Server 2014, and you enable the AutoGrowth property for a database. Even so, changes to the database may not be saved. Additionally, you receive error messages that resembling the following that state that the transaction log is full:

Msg 9002, Level 17, State 2, Line 1
The transaction log for database 'database_name' is full due to 'LOG_BACKUP'.

If you try to back up the transaction log file, you receive the following error message:

Msg 3052, Level 16, State 1, Line 1
BACKUP LOG was unable to log updates for database 'database_name'.

If you try to manually grow the transaction log file, you receive the following error message:

Msg 9002, Level 17, State 1, Line 1
The transaction log for database 'database_name' is full due to 'CHECKPOINT'

If you query the sys.dm_db_log_space_usage DMV, the results indicate that the transaction log is 100-percent or more used. You may also find that there is sufficient free space in the storage drive to accommodate log file growth.

Resolution

This fix is included in Cumulative Update 12 for SQL Server 2014 Service Pack 2.

Each new cumulative update for SQL Server contains all the hotfixes and security fixes that were in the previous build. Check out the latest cumulative updates for SQL Server 2014.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×