First of all, I do not recommend shrinking TemDB files because if you do not resolve the root cause, they will grow again.
What to check:
What to check:
- Long-running queries
- Open transactions
- Poorly written queries
-- Run
FREEPROCCACHE
CHECKPOINT
GO
DBCC FREEPROCCACHE
GO
--Change the size in MB to shrink to---
DECLARE @size NVARCHAR(10) = 18000
DECLARE @info nvarchar(max)
DECLARE @file nvarchar(max)
DECLARE @q1 nvarchar(max)
DECLARE tempdb_cursor cursor for
SELECT NAME FROM sys.master_files WHERE database_id = 2 AND NAME !='templog';
OPEN tempdb_cursor
FETCH NEXT FROM tempdb_cursor into @info
while @@fetch_status = 0
BEGIN
SET @info = @info
SET @q1 = 'USE [tempdb] DBCC SHRINKFILE (''' + @info + ''' , ' + @size + ')'
--EXEC @Q1
PRINT @q1
FETCH NEXT FROM tempdb_cursor
INTO @info
END
CLOSE tempdb_cursor;
DEALLOCATE tempdb_cursor;
CHECKPOINT
GO
DBCC FREEPROCCACHE
--Change the size in MB to shrink to---
DECLARE @size NVARCHAR(10) = 18000
DECLARE @file nvarchar(max)
DECLARE @q1 nvarchar(max)
DECLARE tempdb_cursor cursor for
SELECT NAME FROM sys.master_files WHERE database_id = 2 AND NAME !='templog';
OPEN tempdb_cursor
SET @info = @info
--EXEC @Q1
PRINT @q1
CLOSE tempdb_cursor;
DEALLOCATE tempdb_cursor;
References:
Comments
Post a Comment