Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Change SQL Data Root Directory Expand / Collapse
Author
Message
Posted Tuesday, August 27, 2013 11:21 AM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Monday, September 26, 2016 11:57 PM
Points: 8,234, Visits: 16,383
Placing system dbs on C is not too dramatic as the boot drive it will always be online while the server is up. Obviously tempdb and distribution db should be separated.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1488871
Posted Tuesday, August 27, 2013 11:36 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 23, 2016 6:58 AM
Points: 108, Visits: 501
Well I may have just caught a break. Thanks for your quick responses guys but there probably isn't a point in copying and pasting all the errors now. I was told that only a couple servers need to have their system databases moved, and none of them actually host any data yet. They are all brand new installs, so far it's been quicker and cleaner to just remove SQL and install it all over again with the correct data paths listed.

I thought I was going to have to change about 10 servers that all had been updated with server packs and the systems guys where going to have to reinstall them all. It looks like I notified them in time so they where able to change their install plan for the majority of the servers. Thanks again guys, and yeah I was freaking out a bit.
Post #1488873
Posted Tuesday, August 27, 2013 11:38 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 7:11 AM
Points: 4,717, Visits: 7,335
Well that is good news, however if you post the errors the people willing to help just might be able to help you through the situation...so in the future should you ever need to do something like this again, you will be better prepared?

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1488874
Posted Thursday, April 14, 2016 2:27 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, July 21, 2016 9:51 AM
Points: 4, Visits: 34
Since we will get rid of T drive which I had put as SQL Data Root Directory when I installed SQL 2012SP1 before, so I have moved all system databases from (T drive) drive to another SAN drive (R: drive) and brought up sql running successfully. But I have following concerns before we get rid of T drive...

1. Can I just copy/paste other files /folders over to the R drive without impact bring up sql server?
Other files/folders are (5 MS_AgentSignnningCertificate% files on DATA folder) or folders (Backup, repldata (no data at all) and FTData folder which has 1 folder 'filterData' created on the date installed, and many other old date xml files)

2. The registry key of 'SQLDataRoot' under \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\Setup\ is still showing the old SQL Data root directory 'T:\SQL2012ENT64\SYSTEMDB\MSSQL11.MSSQLSERVER\MSSQL' which I setup before. Is this going to impact sql server running after we get rid of T drive? Or, is there anyway to modify it to the right new drive R without from regedit?

3. Do we have to use exact same folder format (ending with MSSQL11.MSSQLSERVER\MSSQL\) for the new data root directory? I moved all system databases files to the new drive R:\SQL2012ENT64\SYSTEMDB\DATA without any problem to bring up sql server. but not sure if it'll be ok after copy all files over?
Post #1777982
Posted Thursday, April 14, 2016 2:28 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, July 21, 2016 9:51 AM
Points: 4, Visits: 34
Since we will get rid of T drive which I had put as SQL Data Root Directory when I installed SQL 2012SP1 before, so I have moved all system databases from (T drive) drive to another SAN drive (R: drive) and brought up sql running successfully. But I have following concerns before we get rid of T drive...

1. Can I just copy/paste other files /folders over to the R drive without impact bring up sql server?
Other files/folders are (5 MS_AgentSignnningCertificate% files on DATA folder) or folders (Backup, repldata (no data at all) and FTData folder which has 1 folder 'filterData' created on the date installed, and many other old date xml files)

2. The registry key of 'SQLDataRoot' under \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\Setup\ is still showing the old SQL Data root directory 'T:\SQL2012ENT64\SYSTEMDB\MSSQL11.MSSQLSERVER\MSSQL' which I setup before. Is this going to impact sql server running after we get rid of T drive? Or, is there anyway to modify it to the right new drive R without from regedit?

3. Do we have to use exact same folder format (ending with MSSQL11.MSSQLSERVER\MSSQL\) for the new data root directory? I moved all system databases files to the new drive R:\SQL2012ENT64\SYSTEMDB\DATA without any problem to bring up sql server. but not sure if it'll be ok after copy all files ove
Post #1777983
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse