0

I've a new drive to my database, so moved all databases to this new drive. Now I need to move the system databases and the remaining folders that SQL creates such as FTData, JOBS, Log, etc.

How I move all this files? since the current unit (not C:) will be disconnected when all the process is done.

I google it but only find to move database (already done)

EDIT 1: it is a cluster failover installation with Windows failover service

EDIT 2: the SQL installation is in the default location, the files as FTData, Log (the system log) and the mentioned folders are on my E drive and need to move to my new X drive.

Thanks!

marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
Mariano G
  • 255
  • 4
  • 14
  • Honestly, it may just be easier to do a new install and restore a backup. – SQLChao Oct 24 '17 at 18:27
  • You can't move SQLSERVER installation files to another drive completely,but you can move files like FTData, JOBS, Log, etc – TheGameiswar Oct 24 '17 at 18:27
  • for user databases:https://stackoverflow.com/questions/18309677/restoring-database-from-mdf-and-ldf-files-of-sql-server-2008/29053646#29053646 – TheGameiswar Oct 24 '17 at 18:28
  • for system databases:https://learn.microsoft.com/en-us/sql/relational-databases/databases/move-system-databases – TheGameiswar Oct 24 '17 at 18:28
  • I can't wait three hours with all service offline, the DB is 1.5TB. And one thing more to keep in mind is this is a cluster instalation with windows cluster service. – Mariano G Oct 24 '17 at 18:30

2 Answers2

0

This would probably take some time and I have not tested it yet but would assume if you save a complete image of Drive E and used it on Drive X. the application files and application in all would be loaded up and ready for production use when completed without needing to turn off SQL services.

Robert Harris IV
  • 1
  • 3
0

Well, I write this here in case if someone has the same scenario (or similar).

What I did was:

  1. Move all user databases to the new LUN (look at microsoft recomendations)
  2. Move all system database to the new LUN (look at microsoft recomendations)
  3. I searched on the register for my old drive letter (E:), since my old drive was used only for the databases data and some objects created by sql server. And replace in both nodes. Move the MSSQL.... folder from my E: folder to the new LUN.

For the 2th and the 3th step I completly shut down the sql service. And on each database migration, an script was executed to verify that all databases were online.

Here are the keys changed on the register.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft SQL Server\MSSQL12.MSSQLSERVER\CPE\ErrorDumpDir

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft SQL Server\MSSQL12.MSSQLSERVER\Replication\WorkingDirectory

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft SQL Server\MSSQL12.MSSQLSERVER\SQLServerAgent\ErrorLogFile

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft SQL Server\MSSQL12.MSSQLSERVER\SQLServerAgent\WorkingDirectory

Mariano G
  • 255
  • 4
  • 14