• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Moving MSFT SQL Data

D

dawks

Diamond Member
We are running Server 2003 SP2 and SQL Server 2000.

We have created a new array since our old one did not have enough space. I'm wondering if we can just shut down SQL server, move the data to the new array drive, change the drive letter to the previous one, and start the server back up. Will that work? or is there going to be some kind of strange problem (possibly related to time stamps?). I'm hoping as long as the data ends up with the same path, there shouldn't be a problem. Will this work?

Thanks!
 
Whatever you do, make sure you have VALID backups and that you can RESTORE those backups if there is a problem!
 
If you are willing to shut down sql server you can always just detach each database and move the files to the new server and re-attach. You could also do a copy db from server to server if you want to run some tests.
 
If I understand your post correctly, you aren't moving the databases to a new server, just a new (larger) container? If that is the case, stop all SQL services, copy your files to the same directory tree on the new container, change the drive letters assigned to the containers so that the new container has the drive letter assignment that was previously assigned to your now old (small) container and restart SQL services.
 
I just recently did this task moving the databases from a local drive to an iSCSI drive. After the change, as long as the paths are the same and NTFS permissions are the same it will work.
 
I recommend the detach, move, re-attach option.
No telling what kind of problems you may run into if you change drive letters.

I would also check some thing like making sure your logs are getting purged and the databases are getting re-indexed occasionally.

You would be surprised how much space improperly maintained databases will take up over time.
 
Originally posted by: JDMnAR1
If I understand your post correctly, you aren't moving the databases to a new server, just a new (larger) container? If that is the case, stop all SQL services, copy your files to the same directory tree on the new container, change the drive letters assigned to the containers so that the new container has the drive letter assignment that was previously assigned to your now old (small) container and restart SQL services.
Click to expand...

Yes, we are simply moving the data within the server, and this is what we are planning on doing.

Yes we have daily backups of the data.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top