Hi,

I have to move an entire SQL Server system databases from current basic
drive W: to new SAN drive H: in cluster server (current is one node with two
instances). During the installation, I put Program files to C: drive and Data
Files to W: drive. After move all dbs, we will get rid of drive W. My
questions are:

1) Do I need uninstall and reinstall those instances to move system dbs to
new location?

2) Is it possible to following the article 224071 Moving SQL Server
Databases to a New Location with Detach/Attach? If this is the case, after
SQL Server system dbs moved, how about those cluster Configuration files
under the subdirectory FTDATA and config, do I need copy them to new SAN
drive manually since they automatically generated from installation? And what
kind order should I follow, msdb, master, model and tempdb or must master
first? During the move, it need perform many times to Stop and restart SQL
Server, this should be use Cluster Administrator to offline SQL Server
instance or should go to the control panel services manually stop and restart
SQL Server services?

Any input much appreciate,
-Chen

I use the attach method all the time on SQL clusters, works great! You will
need to take SQL down to add the H: drive to the dependency list, if the SAN
does not require the machine(s) to be completely off.

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog

"Chen" <Chen @discussions.microsoft.com> wrote

Hi Rod,

Thanks for the replay. I used detach and attach method for user define
database all the time in cluster server, but this time I am talking about
moving system databases those are master, msdb and model. Compare with
non-cluster server, can I use the similar way to move system databases in
cluster server?

Regards,
-Chen

"Rodney R. Fournier [MVP]" wrote:

Hi Chen and Rod,

I have same question. How move system databases and all other directories of
SQL virtual server (on shared disk) to different location (disk)?

Regards

Richard

"Chen" wrote:

True, I have not moved any of the system databases this way. Let me look
into it.

Rod
"Chen" <Chen (AT) discussions (DOT) microsoft.com> wrote

Hi Rod,

Any result for this issue?

Best Regards,
-Chen

"Rodney R. Fournier [MVP]" wrote:

I can't find a thing, I am hoping Geoff can come to my rescue once again

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog

"Chen" <Chen (AT) discussions (DOT) microsoft.com> wrote

It should work the same. I have moved model, msdb, and tempdb on a cluster
but not master.

Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/default...b;en-us;224071

If you get stuck you can start SQL via the command line from the node
hosting the resource group. Use the correct switch options to point to
master, etc. and then you can use Enterprise Mangler to fix the startup
parameters.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

"Rodney R. Fournier [MVP]" <rod (AT) die (DOT) spam.die.nw-america.com> wrote in
message news:eLfiMyGvEHA.612 (AT) TK2MSFTNGP15 (DOT) phx.gbl...

Hi Geoff,

Thanks for the replay. During the move msdb and model, you need perform the
stop and restart the SQL Server and SQL Agent services. Is this can done in
Cluster Administrator console bring offline SQL instance and bring online, am
I right? Another thing is that after all databases moved, we will get rid of
old drive, how can I treat those cluster Configuration files under the
subdirectory FTDATA and config since they are generate from installation, if
I manually copy them to new SAN drive, the failover should work properly in
the future?

Best Regards,
-Chen

"Geoff N. Hiten" wrote: