Contents
Can we shrink tempdb log file in SQL Server?
If more files are added to tempdb, you can shrink them after you restart SQL Server as a service. All tempdb files are re-created during startup. However, they are empty and can be removed. To remove additional files in tempdb, use the ALTER DATABASE command by using the REMOVE FILE option.
Why tempdb is full in SQL Server?
It might be due to active transactions, versioning or objects required for the SQL Server in the TempDB as per the current workload. Referencing to Microsoft article, we should shrink the TempDB when the SQL Server is in idle mode or the single-user mode.
How to reduce the size of the tempdb transaction log?
Restarting a server instance resizes the transaction log of the tempdb database to its original, pre-autogrow size. This can reduce the performance of the tempdb transaction log. You can avoid this overhead by increasing the size of the tempdb transaction log after starting or restarting the server instance.
How big is tempdb database after SQL server restart?
After restarting the SQL Server service, the tempdb database size went down to 1GB. Doesn’t tempdb maintain its database and transaction log size after a SQL Server restart?
Is there a way to shrink the tempdb database?
Shrinks the size of the specified data or log file for the current database. Make sure to include USE [tempdb] or manually specify the database in Management Studio prior to execution. The SHRINKFILE operation can be stopped at any point in the process with all completed work being retained.
How to reduce the size of a SQL log file?
Log File Auto Shrink Event Class. sys.database_files (Transact-SQL) (See the size, max_size, and growth columns for the log file or files.) You can gain space by enlarging the existing log file (if disk space permits) or by adding a log file to the database, typically on a different disk.