SQL SERVER – TempDB is Full. Move TempDB from one drive to another drive.

When TempDB is Full, I investigate capacity and usage before moving its files. A move requires a planned restart.

The older filegroup error suggested backing up a log. That advice doesn’t apply to TempDB. Temporary data, log use, disk capacity and growth limits need separate investigations.

Check capacity before moving files

Inspect all TempDB data and log files, available disk space, growth settings, and the workload using them. Unlimited growth can’t create more disk space. A different drive is useful only when capacity and I/O arrangements support the change.

-- Read the current logical file names and locations first.
SELECT name, physical_name, size * 8.0 / 1024 AS size_mb
FROM tempdb.sys.database_files;

-- Administrator examples only. These names and paths must match your instance.
ALTER DATABASE tempdb MODIFY FILE
    (NAME = tempdev, FILENAME = N'D:\TempDB\tempdb.mdf');
ALTER DATABASE tempdb MODIFY FILE
    (NAME = templog, FILENAME = N'D:\TempDB\templog.ldf');

Plan the destination and restart

The SQL shows the original logical names as examples. Include every file on your instance. Create the destination folder and grant the SQL Server service account the required access before changing the metadata.

TempDB is recreated at startup. The new file paths take effect after the planned service restart. If the folder or permissions are wrong, startup can fail. Prepare a recovery procedure and a maintenance window first.

After restart, query the file paths again and verify normal operation. Retire former files only after proving that they are no longer in use.

Reference: Moving system database files.

Moving TempDB is not a substitute for capacity planning, it is one possible response to a measured storage problem.

Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.