Skip to main content

Renaming SQL Server Database

Very recently I was working on a data archival module. Project was almost 10+ years old and it kept very sensitive, huge data set. While testing this, accidentally I have deleted some required records from a shared development database which is not awesome at all. Only option that I had was restoring backup files.

But developers who worked with me requested to keep the damage database, since they were not sync schema with the source controller. Only possibility that came to my mind was rename the damaged database and restore backup database with the original name.

As all ways I googled it "how to rename a SQL server database", many articles were listed down in my search result but couldn't find a good all in one article. therefore thought of sharing what I learned.

Understanding what we are going to do with the rename is important.Mainly this process can divided into three parts,
  1. Rename Database
  2. Rename Mappings
  3. Rename Files
Following the order of above three parts are necessary. And if you see closely renaming a database will leads to three different renames.  

Below image indicates very low level picture of the components that we are going to rename


Rename Database

Below image indicates Original database,
Right click on the database -> Select Properties -> Select Files tab.



This will be the first step. Once we completed this part, database rename will be visible in the SQL Server Management Studio - Object Explorer. Let's rename the database.

USE master
GO

ALTER DATABASE OriginalDB 
SET SINGLE_USER 
WITH ROLLBACK IMMEDIATE
GO

EXEC master..sp_renamedb 'OriginalDB','RenameDB'
GO

ALTER DATABASE RenameDB 
SET MULTI_USER 
GO



Special point you can see in the code is set user accessibility to single user before going to rename the database. Once rename is completed alter database back to multi user accessibility. This will ensure withing that time period no one else can access the database.

Rename Mappings

Result of below query excution gives you the logical file names of the database files.

USE master
GO

-- Identify Database File Names --

SELECT name AS [Logical Name], 
       physical_name AS [DB File Path],
       type_desc AS [File Type],
       state_desc AS [State] 
FROM   sys.master_files
WHERE  database_id = DB_ID(N'RenameDB')
GO



Though we renamed the databases, Logical files are yet to rename. That will be the second step. In this step again you have to alter database user accessibility to single. Probably you have noticed that I haven't alter it to multi user again. I have done this purposely because till we complete entire process we cannot gran this permission again.

-- Set Database as a Single User --
ALTER DATABASE [RenameDB] SET SINGLE_USER WITH ROLLBACK IMMEDIATE

-- Change Logical File Name --
ALTER DATABASE [RenameDB] MODIFY FILE (NAME=N'OriginalDB', NEWNAME=N'RenameDB')
GO
ALTER DATABASE [RenameDB] MODIFY FILE (NAME=N'OriginalDB_log', NEWNAME=N'RenameDB_log')
GO



After successful execution you can re-run the above query (Query that list down database file information). Files should be renamed to your new names. But still you can see the physical file with the old name. Next step is to rename that.


Rename Files

As you can see, physical files of logical files are still in the original name. Next thing is to rename the physical file names. Navigate to DB File Path. Find physical files.



Before you rename make sure you detached the database first.

/* Detach Current Database */
USE [master]
GO
EXEC master.dbo.sp_detach_db @dbname = N'RenameDB'
GO

Once you detached the database you can rename these files using xp_cmdshell in SQL Server or manually from the file exporer (use desired way). In my case I used manual renaming.



When file rename completed next is to re attached the database. Below query attached database back. Also make sure to grant multi user accessibility back.

/* Attach Renamed RenameDB Database Online */
USE [master]
GO
CREATE DATABASE RenameDB ON 
( FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\RenameDB.mdf' ),
( FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\RenameDB_log.ldf' )
FOR ATTACH
GO

ALTER DATABASE RenameDB 
SET MULTI_USER 
GO



To ensure everything renamed properly you can re-run the query that shows logical file names of the database.



This will end a successful database rename :)

May the force be with you! 

Comments

Popular Posts

SSAS: The Sort Order Specified For Distinct Count Records Is Incorrect.

Symptoms During a processing time of a cube that contains a distinct count measure, the process fails with the following error message: The sort order specified for distinct count records is incorrect Cause This is most likely caused by different sort order used on the data warehouse data set and the analysis service database data set. Resolution Modify the sort order of the data warehouse data set so that it will match with the analysis service database data set. Into the Depth  Navigate to the analysis database and start to process the desired database. When the processing begins, the Process progress window will pop up. Wait till the process gets failed. After the process failed, find the failing measure group and expand to the last node where you can see an SQL query. Double click on the query and view the details. This query gives you the exact order by the column which caused you this trouble.  Execute the query using the data warehouse datab...

Dynamic Assembly in C#

Static Assembly Vs Dynamic Assembly Static Assemblies are those assemblies which are stored on the disk permanently as a file or set of files. Since these assemblies are stored in the disk, those are only loaded when CLR requests.  These are the assemblies we are dealing with daily. Assemblies that I'm going to talk about today bit different. It completely opposite of the Static Assemblies. Those Assemblies are not stored on the disk before execution. When an application requires any type, which references from these assemblies, DOT NET will create these Assemblies at the runtime so that it will directly load into the memory. Why is it important ? Like I mentioned, this is not something we do very often. It is not all about how important it is. Personally, I think it is better to know this kind of hidden language features. More you play with this more you learn. I found cool stuff I can do with this. Hope it will be same for you as well. This is an old feature. How ...

global.json file

  Symptoms Suddenly you get build errors in your build pipeline which perfectly builds in your local machine 🤔🤔🤔 Cause Most likely the root cause is .NET SDK versions. Your local machine builds on a different SDK and the pipeline builds on a different SDK. Resolution The ideal way of solving this is to force everyone to use one define .Net SDK. Regardless of whether it is a developer or CI pipeline. Simply to make this happen .NET  provides you a file called "global.json". The global.json file allows you to define which .NET SDK version is used when you run .NET CLI commands. Selecting the .NET SDK version is independent from specifying the runtime version a project targets. For information about specifying the runtime version instead of the SDK version, see Target frameworks . If you always want to use the latest SDK version that is installed on your machine, no global.json file is needed. Into the Depth The sample global.json file looks like the below, {    ...