15 pts.
 Adding and removing disk space for SQL2000
The scenario:SQL_SVR_A (2000)has x amount 'too much' SAN disk space that they want to reclaim/use to allocate to SQL_SVR_B (2000)- which doesn't have enough space. What is the best method to 1)remove the disk space and keep all db's in-tact (backup/recovery?, or another way??) and 2)how to add the new space to the server B, keeping the db's in-tact (or possibly re-aligning them to alternate locations on the new space)? Thank you for any input!

Software/Hardware used:
ASKED: February 11, 2010  4:35 PM
UPDATED: February 11, 2010  9:02 PM

Answer Wiki:
To do this you'll need to create a new LUN on the SAN and present it to SQL_SVR_A. Then stop the SQL Server, move the database files to the new smaller drive, keeping all the folder paths the same. Switch the drive letters on the two volumes. Then start the SQL Server Service again. All your databases will now be available. You can now reclaim the empty volume back on the SAN, delete the LUN, and extend the existing LUN on SQL_SVR_B onto the new empty space.
Last Wiki Answer Submitted:  February 11, 2010  8:34 pm  by  Denny Cherry   64,505 pts.
All Answer Wiki Contributors:  Denny Cherry   64,505 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

Thank you very much for the reply, I appreciate you taking the time to answer!
However, if you would please explain a little deeper?

When you say move the databases to the new drive, keeping the paths the same:

- should the drive letters and paths already be defined on this smaller drive/LUN, or do you mean that the same paths should be defined on different drive letters (there are 11 f: through p:), aka f: = q, g:=r, etc…then once the files are copied, and the original LUN is disabled/removed, rename the drive letters to the original?

Thank you, again..

 15 pts.