There's no problem with doing this, just make sure that you copy over the file permissions as well (or grant permissions to the new service account if you're using one).
You should also read the MSDN document that outlines how to move user databases (if you're remaining on the same SQL instance and just provisioning a new disk). Rather than detach the database you should take it offline when moving the files.
https://msdn.microsoft.com/en-us/library/ms345483(v=sql.110).aspx
After bringing the database back online run checkdb just to make sure everything is ok.
- Edited by jmcmullen Thursday, March 26, 2015 11:41 AM
- Proposed as answer by Michelle LiMicrosoft contingent staff, Moderator Thursday, March 26, 2015 1:20 PM
Yes you can use robocopy to copy files
http://sqlserverdb.blogspot.in/2012/06/robocopy-files-to-another-drive.html
I would suggest to take database offline instead of stopping SQL. That way you will be able to move 1 database at a time and less downtime.
- Proposed as answer by Michelle LiMicrosoft contingent staff, Moderator Thursday, March 26, 2015 1:20 PM
Hi Mika,
I have different thoughts here instead f migrating using robocopy please use Backup and restore mechanism in SQL Server to move database. This is MUCH BETTER than all other methods
You dont have to take database offline
You dont have to take SQL Server offline.
Please read Copy database using backup and Restore.