August 5, 2015 at 3:46 pm
We are going to migrate our production databases (just one server) from 2008 R2 to 2014, and it will be on a new hardware.
On our old server all database files located on a default folder like M:\Program Files\Microsoft SQL Server\MSSQL\Data\File_name.mdf
We have decided that on a new server it should be shorter and simpler, like:
M:\Data\File_name.mdf
L:\Logs\File_name.ldf
etc.
But my concern is there are any implications of this change? Are there any internal SQL Server processes or scripts that rely on pseudo-standard [Drive Letter]:\Program Files\Microsoft SQL Server\MSSQL\Data\... location?
Our cumulative database size is close to 2 TB, we use log shipping + failover clustering for DR, but eventually will migrate to AlwaysOn. We have lots of linked servers to other servers, we don't use filestreams or anything like that, and we have very small number of SSIS packages.
Thanks
August 6, 2015 at 3:32 am
Hi,
There should be no problems moving DBs to a different path location. Only if you have read-only databases or read-only filegroups you may find some issues. Maybe if you are using FILESTREAM filegroups you will get any small problems. I guess you are not performing an in-place upgrade but even in that case you can change user and system database location.
You can set a VM environment for migration process training and get comfortable with all difficult steps.
August 6, 2015 at 4:46 am
SQL Guy 1 (8/5/2015)
But my concern is there are any implications of this change? Are there any internal SQL Server processes or scripts that rely on pseudo-standard [Drive Letter]:\Program Files\Microsoft SQL Server\MSSQL\Data\... location?Our cumulative database size is close to 2 TB, we use log shipping + failover clustering for DR, but eventually will migrate to AlwaysOn. We have lots of linked servers to other servers, we don't use filestreams or anything like that, and we have very small number of SSIS packages.
Thanks
The paths are more or less transparent, are you going to backup\restore or detach\attach the databases to move them?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 6, 2015 at 7:14 am
JManuelN (8/6/2015)
Hi,There should be no problems moving DBs to a different path location. Only if you have read-only databases or read-only filegroups you may find some issues. Maybe if you are using FILESTREAM filegroups you will get any small problems. I guess you are not performing an in-place upgrade but even in that case you can change user and system database location.
You can set a VM environment for migration process training and get comfortable with all difficult steps.
I have read-only filegroups (they are historical partitions), but as I mentioned above, I don't have filestreams. We migrate it to another, new hardware.
August 6, 2015 at 7:15 am
Perry Whittle (8/6/2015)
SQL Guy 1 (8/5/2015)
But my concern is there are any implications of this change? Are there any internal SQL Server processes or scripts that rely on pseudo-standard [Drive Letter]:\Program Files\Microsoft SQL Server\MSSQL\Data\... location?Our cumulative database size is close to 2 TB, we use log shipping + failover clustering for DR, but eventually will migrate to AlwaysOn. We have lots of linked servers to other servers, we don't use filestreams or anything like that, and we have very small number of SSIS packages.
Thanks
The paths are more or less transparent, are you going to backup\restore or detach\attach the databases to move them?
Backup/restore. And keep that backup for indefinite period of time.
August 6, 2015 at 8:49 pm
There wont be any issues. Just use MOVE command on your restore script for an alternate location for db files.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply