"Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
message news:e2v4pdr8EHA.3260@TK2MSFTNGP14.phx.gbl...
[quoted text, click to view] > Detach/Attach is a very popular approach, and the way I like to do it.
And funny enough, I was JUST doing this on a production server:
sp_detach_db DB_FOO
go
master..xp_cmdshell 'move f:\sql_log\DB_FOO_log.ldf
J:\sql_log\DB_FOO_log.ldf'
go
sp_attach_db DB_FOO,
@filename1='E:\SQL_Data\data\DB_FOO_Data.MDF',
@filename2='J:\sql_log\DB_FOO_log.ldf',
@filename3='g:\sql_index\DB_FOO_Index_Data.NDF'
Moving the LOG file from F: to J: (direct attached storage to the SAN)
With 500 MB log file, was taking about 50 seconds. This speed of course
varies based on your disk subsystems.
[quoted text, click to view] >
> See
http://support.microsoft.com/kb/224071/EN-US/ for more details.
>
> Cheers,
>
> Rod
>
> MVP - Windows Server - Clustering
>
http://www.nw-america.com - Clustering
>
http://msmvps.com/clustering - Blog
>
> "polar" <polar@discussions.microsoft.com> wrote in message
> news:F36A4FA6-FD47-439A-A937-D82411448D29@microsoft.com...
> > Hello,
> > I appreciate any suggestions or comments on the following.
> >
> > We have active/active cluster, SQL 2000, Win 2000. All databases on
first
> > instance/node are on drive E, and second instance/node on drive F. We
are
> > trying to move all database files to new drives, P and Q respectively.
> >
> > One approach would be to detach all databases, move files to new drive,
> > and
> > re-attach.
> >
> > Another alternative would be to ...
> > 1. stop SQL Server resource
> > 2. copy all database files to new drive P
> > 3. assign old drive letter E to new drive P
> > 4. restart cluster group
> >
> > The end result is that the database files or on a new drive, labelled as
> > the
> > old drive letter, which is OK.
> >
> > Anyone see any problems with the second approach?
> >
> > Thanks in advance,
> > Paul
>
>
