Assume that you are using Microsoft SQL Server 2012 or SQL Server 2014. When the log file of tempdb database is full, SQL Server crashes, and you receive the following error message:
Error: 9002, Severity: 17, State: 4.
The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'.
Error: 3314, Severity: 21, State: 3.
During undoing of a logged operation in database 'tempdb', an error occurred at log record ID (135:376:442). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Error: 3449, Severity: 21, State: 1.
SQL Server must shut down in order to recover a database (database ID 2). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
This issue occurs if the size of the tempdb log file is not enough to handle tempdb workload, and the auto growth of the log file is set to Off. If a rollback fails in tempdb because of limited space, SQL Server crashes.
This hotfix enables a more precise calculation of reserved space when the log runs out of space. This hotfix also helps avoid rollback failure in tempdb by enabling the tempdb log grow temporarily. These changes help prevent server crashes.
Service pack information for SQL Server 2014
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2014. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2958069 How to obtain the latest service pack for SQL Server 2014
For more information about SQL Server 2014 Service Pack 1 (SP1), see bugs that are fixed in SQL Server 2014 Service Pack 1.
Service pack information for SQL Server 2012
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2012. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2755533 How to obtain the latest service pack for SQL Server 2012
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.