November 24, 2011 at 6:16 am
Don't, or reinstall SQL Server.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 24, 2011 at 6:27 am
Why do you have to move those files???
It's not like they are taking 100 GB!
November 24, 2011 at 6:38 am
I have to move it from E to C or D drive as E drive is dying. Is there any way to move it without re-installing?
November 24, 2011 at 6:45 am
could you move all the contents of the current E drive to the new drive, then re-label the new drive as the E? SQL would need to be stopped.
Otherwise its a reinstall
---------------------------------------------------------------------
November 24, 2011 at 6:47 am
sorry just reread your post, if the E drive is going completely not to be replaced, its a reinstall
---------------------------------------------------------------------
November 24, 2011 at 6:51 am
that's right.... The E drive is going out of picture completely. So what options I have?
November 24, 2011 at 6:53 am
>
george sibbald (11/24/2011)
sorry just reread your post, if the E drive is going completely not to be replaced, its a reinstall
November 24, 2011 at 6:56 am
Reinstall.
But why is the E drive dying? You would actually be better off moving your system databases from the C to the E in terms of best practice configuration.
---------------------------------------------------------------------
Viewing 8 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply