We have our production SQL 2005 server (64 bit Standard Ed.) attached to an
iSCSI Equalogic SAN. We have set up 2 new servers an installed the cluster
service. My question is: can I install SQL 2005 in this cluster environment
and latter on disconnect the data and log volumes from the production server,
attach those volumes to the cluster an reattach the DBs? the reason we need
to do it like that is that we don't have enough spare space in the SAN to
initially create these 2 volumes in the cluster.

Any ideas/suggestions would be greatly appreciated.

If I understand what you are asking, you want to be able to present the
LUNs--that are currently being used by your prod server--to your new cluster
instance instead. Yes, absolutely. The overall process is simple, but there
are details you need to apy attention. Details include such things as making
sure that the SQL instance on your new cluster is installed exactly the same
as your prod. This is not absolutely necessary since you can always tweak
registry entries to make it work. But you can save yourself tons of grief by
keeping the two installs identical (except server name and IP).

Linchi

"Carlos" wrote:

If I understand what you are asking, you want to be able to present the
LUNs--that are currently being used by your prod server--to your new cluster
instance instead. Yes, absolutely. The overall process is simple, but there
are details you need to apy attention. Details include such things as making
sure that the SQL instance on your new cluster is installed exactly the same
as your prod. This is not absolutely necessary since you can always tweak
registry entries to make it work. But you can save yourself tons of grief by
keeping the two installs identical (except server name and IP).

Linchi

"Carlos" wrote:

If I understand what you are asking, you want to be able to present the
LUNs--that are currently being used by your prod server--to your new cluster
instance instead. Yes, absolutely. The overall process is simple, but there
are details you need to apy attention. Details include such things as making
sure that the SQL instance on your new cluster is installed exactly the same
as your prod. This is not absolutely necessary since you can always tweak
registry entries to make it work. But you can save yourself tons of grief by
keeping the two installs identical (except server name and IP).

Linchi

"Carlos" wrote:

If I understand what you are asking, you want to be able to present the
LUNs--that are currently being used by your prod server--to your new cluster
instance instead. Yes, absolutely. The overall process is simple, but there
are details you need to apy attention. Details include such things as making
sure that the SQL instance on your new cluster is installed exactly the same
as your prod. This is not absolutely necessary since you can always tweak
registry entries to make it work. But you can save yourself tons of grief by
keeping the two installs identical (except server name and IP).

Linchi

"Carlos" wrote:

If I understand what you are asking, you want to be able to present the
LUNs--that are currently being used by your prod server--to your new cluster
instance instead. Yes, absolutely. The overall process is simple, but there
are details you need to apy attention. Details include such things as making
sure that the SQL instance on your new cluster is installed exactly the same
as your prod. This is not absolutely necessary since you can always tweak
registry entries to make it work. But you can save yourself tons of grief by
keeping the two installs identical (except server name and IP).

Linchi

"Carlos" wrote:

If I understand what you are asking, you want to be able to present the
LUNs--that are currently being used by your prod server--to your new cluster
instance instead. Yes, absolutely. The overall process is simple, but there
are details you need to apy attention. Details include such things as making
sure that the SQL instance on your new cluster is installed exactly the same
as your prod. This is not absolutely necessary since you can always tweak
registry entries to make it work. But you can save yourself tons of grief by
keeping the two installs identical (except server name and IP).

Linchi

"Carlos" wrote:

If I understand what you are asking, you want to be able to present the
LUNs--that are currently being used by your prod server--to your new cluster
instance instead. Yes, absolutely. The overall process is simple, but there
are details you need to apy attention. Details include such things as making
sure that the SQL instance on your new cluster is installed exactly the same
as your prod. This is not absolutely necessary since you can always tweak
registry entries to make it work. But you can save yourself tons of grief by
keeping the two installs identical (except server name and IP).

Linchi

"Carlos" wrote:

If I understand what you are asking, you want to be able to present the
LUNs--that are currently being used by your prod server--to your new cluster
instance instead. Yes, absolutely. The overall process is simple, but there
are details you need to apy attention. Details include such things as making
sure that the SQL instance on your new cluster is installed exactly the same
as your prod. This is not absolutely necessary since you can always tweak
registry entries to make it work. But you can save yourself tons of grief by
keeping the two installs identical (except server name and IP).

Linchi

"Carlos" wrote:

If I understand what you are asking, you want to be able to present the
LUNs--that are currently being used by your prod server--to your new cluster
instance instead. Yes, absolutely. The overall process is simple, but there
are details you need to apy attention. Details include such things as making
sure that the SQL instance on your new cluster is installed exactly the same
as your prod. This is not absolutely necessary since you can always tweak
registry entries to make it work. But you can save yourself tons of grief by
keeping the two installs identical (except server name and IP).

Linchi

"Carlos" wrote: