I have this same issue, can't figure out why Sql Server does not have this documented.
2 node Sql Server 2005 64 bit enterprise.
I have moved all databases without issue using:
Now I could not connect using this method for a cluster setup. It works moving master and resource when not clustered. I was getting connection errors when attempting to move the resource using sqlcmd an the net start service part. So I found this and other links in this forum. I seems to be the closest to reality that I can find.
So here is my steps that I will attempt for this cluster to move master and resource databases:
1)From Cluster Administrator: stop the cluster service for the failover node
2)From Cluster Administrator: take the SQL Server resource offline
OS Move master data and log files to new location below.
3)From SQL Server Configuration Manager: add the startup parameters -f;-T3608
Original configuration manager startup parameters:
-dE:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf;-eE:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG;-lE:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
To:
-dM:\MSSQL\MSSQL.1\MSSQL\Data\master.mdf;-eM:\MSSQL\MSSQL.1\MSSQL\LOG\ERRORLOG;-lM:\MSSQL\MSSQL.1\MSSQL\Data\mastlog.ldf;-f;-T3608
4)From Cluster Administraror: bring the SQL Server resource online again
5) Run from command line (This is where it failed before, crossing fingers):
sqlcmd -sMSSQLSERVER
6) From sqlcmd:
ALTER DATABASE mssqlsystemresource
MODIFY FILE (NAME=data, FILENAME= 'M:\MSSQL\MSSQL.1\MSSQL\Data\mssqlsystemresource.mdf');
GO
ALTER DATABASE mssqlsystemresource
MODIFY FILE (NAME=log, FILENAME= 'M:\MSSQL\MSSQL.1\MSSQL\Data\mssqlsystemresource.ldf');
GO
7) OS move the files in step 6 to new location
8) From sqlcmd:
ALTER DATABASE mssqlsystemresource SET READ_ONLY;
go
exit
9) From SQL Server Configuration Manager: remove the startup parameters -f;-T3608
-dM:\MSSQL\MSSQL.1\MSSQL\Data\master.mdf;-eM:\MSSQL\MSSQL.1\MSSQL\LOG\ERRORLOG;-lM:\MSSQL\MSSQL.1\MSSQL\Data\mastlog.ldf
10) From Cluster Administrator: take the SQL Server resource offline
11) From Cluster Administrator: start the cluster service for the failover node
12) From Cluster Administraror: bring the SQL Server resource online again.
Anyone who got there setup working, what do you think?