Skip to main content

How to change the "tempdb" file path in SQL Server

The tempdb database is one of the system databases of SQL server, it is available for all users connected to that sql instance. "tempdb" is re-created every time the sql server instance is getting started. You don't have to physically move the data and log files.
Sometimes we're getting the error that drive is full. 

Msg 9002, Level 17, State 6, Line 1
The log fie for database 'tempdb' is full. Backup the transaction log for the database to free up some log space.

Let's see how to change the tempdb file path.
Step1. First check the tempdb file path and name using below query 

USE tempdb;

GO
EXEC sp_helpfile;

-- -- -- -- We'll get output like this


    


            name
            fileid
            filename
            filegroup
            size
            maxsize
            growth
            usage            
        


    


            tempdev
            1
            \tempdb.mdf
            PRIMARY
            8192 KB
            Unlimited
            10%
            data only            
        



            templog
            2
            \tempdb.ldf
            NULL
            512 KB
            Unlimited
            10%
            data only

Step2. Now chose the filepath for new location of your tempdb. Now let's say you want to move tempdb to new drive (e.g. "H:\SQLFiles\SQLServer\") 
USE master;

-- -- Now let's say you want to move tempdb to new drive (e.g. "H:\SQLFiles\SQLServer\")
-- --

ALTER DATABASE tempdb MODIFY FILE
(Name = tempdev, FileName='H:\SQLFiles\SQLServer\tempdb.mdf')

GO
ALTER DATABASE tempdb MODIFY FILE
(Name = templog, FileName = 'H:\SQLFiles\SQLServer\tempdb.ldf')

After executing the above query, restart the sql instance. The files are created in the new location when the service is restarted. Until the service is restarted, "tempdb" continues to use the data and log files in existing location. You can delete the tempdb from previous location.

Comments

Post a Comment

Popular posts from this blog

EFCore - Collate function

Search in SQL server query is generally case insensitive (by default or based on database level collation). Suppose we have an employees table with a row having first-name column value as "My-First-Name", so if we want to do the case-sensitive search we have to explicitly use the related collate: In EF 5 (currently in Release Candidate version [RC.2.20475.6]) Collate function got introduced which helps us to use our specific collation based search.  C# with EF5 code sample: var employeeCaseSensitiveSearch = _dbContext.Employees .Where(x => EF.Functions.Collate(x.FirstName, "Latin1_General_CS_AS") == "my-first-name") .FirstOrDefault(); A related database query will be something like this: T-SQL: Case sensitive search (use specific collation e.g.: Latin1_General_CS_AS) SELECT * FROM dbo.Employees AS e WHERE e.FirstName Collate Latin1_General_CS_AS = 'my-first-name' Some of the useful CSharp function which g...
Post a Comment
Read more

Git - Update submodule

Sometimes in the large project when we separate it in different repositories we need to take reference of one repository in another where some the sub-module concepts. Now if we move our submodule to a different repository or renaming its repo-path then we've to also update the repository where this sub-module is getting referenced. Let's see how to update the git submodule.  Step-1: First clone the repo Step-2: Open git UI to create a new local branch from master  Step-3: Open git bash -- Now run below command to (remove submodules & add them):  -- Remove submodule git submodule deinit YOUR_FIRST_REPO git rm YOUR_FIRST_REPO git commit -m "Removed submodule YOUR_FIRST_REPO" rm -rf .git/modules/YOUR_FIRST_REPO -- Add submodule git submodule add <<..YOUR_FIRST_REPO git URL>> Step-4: All good, let's push our changes to the master
Post a Comment
Read more

EFCore - Update command is not updating the underlying data

Why my update command using EFCore is not updating the underlying data in the database though in middle-tier code it's successful, not throwing any error? Let's try to get the root cause and how to solve this.  When creating the model class of related database object if the primary key name is Id then no need to explicitly mention the Key in ef-core OnModelCreating.  But if we've key name different from Id then we have to explicitly mention it in our OnModelCreating. Something like this:  entity.HasKey(c => new {c.CustId }); Assume in the database we've Customers table like this: CREATE TABLE [dbo].[Customers]( [CustId] [INT] IDENTITY(1,1) NOT NULL Primary Key, [FirstName] [VARCHAR](50) NULL ) Point to ponder: In the database table, column CustId is already defined as Primary key.  In EFCore model setup, it's up to us to configure the Key as (custId) or configure it as HasNoKey() Assume we've set our entity with Ha...
Post a Comment
Read more