Review TempDB file size and location and move to New Drive or Folder

Here are some quick scripts to find details about TempDB.  One thing I dislike about other scripts is that they calculate the MB size by [SIZE]*8/1024 which can be reduced to simply 128.  The other important thing to remember about TempDB is that it is different than a User Created databases as it is recreated on every start up or restart of the SQL Server Service and must look to the master database for its start-up configuration. Any tempdb file growth via ALTER DATABASE works like a user DB but tempdb differs in that it allows the ALTER DATABASE command to re-size a data file to a smaller value upon start/restart, without actually changing the current file size or shrinking out the space. Thus setting a new smaller value is held in master as the initial start-up size and leveraging this makes resizing TempDB as well as adding files to tempdb easier.  

If you ever have to refer to Shrinking tempdb without restarting SQL Server or When Shrinking Tempdb Just Won’t Shrink then you know that just getting things back to a working state is the most important and not everyone can take an outage so having this sitting idle waiting for a restart is great!  If you get into trouble then refer to: How to Start SQL Server Service Without tempdb?


Example: 
-- Get TempDB(Database_ID = 2) File Path info for configured size and current size
USE [master];
GO

--Configured
SELECT DB_NAME( DATABASE_ID ) db_name, file_id, type_desc, name, physical_name, size / 128.0 AS CurrentSizeMB
      ,growth / 128.0 AS CurrentGrowthMB
  FROM sys.master_files
 WHERE database_id = DB_ID( 'tempdb' )
 ORDER BY type_desc DESC, file_id;
GO

--Current size
SELECT 'tempdb' AS db_name, file_id, type_desc, name, size / 128.0 [TempdbSizeInMB], growth / 128.0 [TempdbGrowthInMB]
  FROM tempdb.sys.database_files
 ORDER BY type_desc DESC, file_id;
GO

-------------------------------------------------------------
-- Generate Alter Statement for New File Location = Update @NewPath = 'HERE'
DECLARE @NewPath VARCHAR(254);
SET @NewPath = 'T:\MSSQL\DATA\';

SELECT 'ALTER DATABASE tempdb MODIFY FILE (NAME = [' + f.name + '],' + ' FILENAME = ''' + @NewPath + '' + f.name
       + CASE
              WHEN f.type = 1 THEN '.ldf'
              ELSE '.mdf' END + ''');'
  FROM sys.master_files f
 WHERE f.database_id = DB_ID( N'tempdb' );
-------------------------------------------------------------
-- Generate Syntax for TempDB Datafiles 'ROWS' upon restart of SQL Service
-- Update @ReStart_Size = 'SIZE = XXXMB , FILEGROWTH = XXXMB'; 
DECLARE @ReStart_Size VARCHAR(254);
SET @ReStart_Size = 'SIZE = 200MB , FILEGROWTH = 100MB';

SELECT 'ALTER DATABASE tempdb MODIFY FILE (NAME = [' + f.name + '],' + ' ' + @ReStart_Size + ');'
  FROM sys.master_files f
 WHERE f.database_id = DB_ID( N'tempdb' )
 AND f.type_desc='ROWS';
 

Comments

Post a Comment

Popular posts from this blog

How to mass update all or some sql server agent job step commands

How to mass update all or some sql server agent job step and commands using TSQL.   This will use the built-in Replace function to search text in SQL agent jobs  SQL Agent Job information is stored in MSDB and can reviewed using some of the following queries: SELECT * FROM msdb.dbo.SysJobs SELECT * FROM msdb.dbo.SysJobSteps -- OR SELECT a.name as job_name, b.step_name, b.subsystem, b.command, b.database_name, a.enabled       ,a.description, a.date_created, b.job_id, b.step_id   FROM [dbo].[sysjobsteps] as b   INNER JOIN sysjobs as a ON a.job_id = b.job_id Since I will be focusing on the Commands column I will look at using this query to extract data into a temp table so that I can test any updates with the replace step before doing an update to MSDB. This would be your opportunity to archive or save any commands as needed.  Some people may prefer to generate all the syntax necessary to use EXEC sp_update_jobstep so you a...
Read more

SQL Monitoring for Blocking and Locking Capture and Log to table with sp_WhoIsActive or sp_BlitzWho

Image
You can use  sp_WhoIsActive or sp_BlitzWho and log the capture data to a table.   In my example I will use sp_whoisactive as I am more familiar with its use and data collection, however I will look at creating a future post using BlitzWho.  I will provide a few examples that were used to determine that the paid SQL monitoring products can be fancy tools but can be useless if you don't understand the basic concepts or even an understanding of how we capture similar data or in some cases more finely tuned to a specific scenario or use case.  Sometimes these paid solutions are incorrect or things can simply go wrong (Services Fail to start or the data is aggregated and misses something like the query commands and SQL Fragments) and it's always good to plan ahead and be prepared.   Sp_WhoIsActive is a procedure written by Adam Machanic. It can be found here:  sp_whoisactive downloads Sp_BlitzWho is a procedure written by the Brent Ozar team....
Read more

SQL Server General Index Naming Convention

SQL Server General Index Naming Convention  easy to follow:  PK_ for primary keys PK_  Primary Keys, which are logical constructs and not necessarily physical constructs, get tagged with a PK_ prefix. In most systems that I design the PK_ isn’t a clustered index.  IX_ for non clustered non unique indexes IX_  standard single or even multi-column indexes used for seeks or intersection just get prefixed with an IX_ (for  I nde X ). In cases where I need a composite index (i.e., multiple columns) but still explicitly ‘tolerate’ key/bookmark lookups, I’ll still call my seek/intersection/composite indexes IXes. UK_ for unique keys UK_  for unique key index UX_ for unique indexes UX_  for unique index. CLIX_ for Clustered Index (non PK) CLIX_  (non-PK) Clustered Index name is prefixed with CLIX (for  CL ustered  I nde X ) Additionally, I like to code all Create Indexes in SQL 2012 and above with an if not ...
Read more