Is it OK to shrink tempdb log?

Question

In SQL Server 2005 and later versions, shrinking the tempdb database is no different than shrinking a user database except for the fact that tempdb resets to its configured size after each restart of the instance of SQL Server. It is safe to run shrink in tempdb while tempdb activity is ongoing.

Can we shrink tempdb log file in SQL Server?

We can use the DBCC SHRINKFILE command to shrink the data or log file for the TempDB. We do not need a restart of SQL Service in this case.

Can we shrink log files?

To shrink a data or log file. In Object Explorer, connect to an instance of the SQL Server Database Engine and then expand that instance. Expand Databases and then right-click the database that you want to shrink. Point to Tasks, point to Shrink, and then click Files.

What happens if tempdb is full?

The TempDB database is special in many ways, but an interesting aspect is that when its files automatically grow when they become full, this growth is not persisted and will be undone on the next restart of the SQL Server service.

Does tempdb affect performance?

Although this may be true on smaller, less active SQL Server instances, tempdb can significantly affect SQL Server's performance. DBAs can act to ensure that tempdb performance is optimized and to optimize the overall performance of SQL Server.

Expert · Answer