We are running an active/active SQL Server cluster with 4 named instances of
SQL Server 2000. We run 2 instances on each cluster node. We would like to
perform an in-place migration to sql server 2005 of one of the SQL Server
instances. We don't have a "test" cluster to work with. I'm wondering what
the risk level is for the instance that we are planning to migrate in place
as well as the remaining SQL Server 2000 instances on the cluster. Are you
able to direct me to any further readings on this topic?

You may start with creation of a new sqlserver2005 cluster instance
with its own new resources.
You will then need to copy any SQLServer dependencies, such as logon
accounts. After that, you can use a log shipping solution to
syncronize the two istances. There are some alternatives like execute
a copy database or a database mirroring solution or detach/attach the
database files.
When the new istance will be sincronized and your tests on it will be
positive, you can switch to the new cluster and then reconnect
apllications.

Regards
Riccardo

You may start with creation of a new sqlserver2005 cluster instance
with its own new resources.
You will then need to copy any SQLServer dependencies, such as logon
accounts. After that, you can use a log shipping solution to
syncronize the two istances. There are some alternatives like execute
a copy database or a database mirroring solution or detach/attach the
database files.
When the new istance will be sincronized and your tests on it will be
positive, you can switch to the new cluster and then reconnect
apllications.

Regards
Riccardo

You may start with creation of a new sqlserver2005 cluster instance
with its own new resources.
You will then need to copy any SQLServer dependencies, such as logon
accounts. After that, you can use a log shipping solution to
syncronize the two istances. There are some alternatives like execute
a copy database or a database mirroring solution or detach/attach the
database files.
When the new istance will be sincronized and your tests on it will be
positive, you can switch to the new cluster and then reconnect
apllications.

Regards
Riccardo

You may start with creation of a new sqlserver2005 cluster instance
with its own new resources.
You will then need to copy any SQLServer dependencies, such as logon
accounts. After that, you can use a log shipping solution to
syncronize the two istances. There are some alternatives like execute
a copy database or a database mirroring solution or detach/attach the
database files.
When the new istance will be sincronized and your tests on it will be
positive, you can switch to the new cluster and then reconnect
apllications.

Regards
Riccardo

You may start with creation of a new sqlserver2005 cluster instance
with its own new resources.
You will then need to copy any SQLServer dependencies, such as logon
accounts. After that, you can use a log shipping solution to
syncronize the two istances. There are some alternatives like execute
a copy database or a database mirroring solution or detach/attach the
database files.
When the new istance will be sincronized and your tests on it will be
positive, you can switch to the new cluster and then reconnect
apllications.

Regards
Riccardo

You may start with creation of a new sqlserver2005 cluster instance
with its own new resources.
You will then need to copy any SQLServer dependencies, such as logon
accounts. After that, you can use a log shipping solution to
syncronize the two istances. There are some alternatives like execute
a copy database or a database mirroring solution or detach/attach the
database files.
When the new istance will be sincronized and your tests on it will be
positive, you can switch to the new cluster and then reconnect
apllications.

Regards
Riccardo

You may start with creation of a new sqlserver2005 cluster instance
with its own new resources.
You will then need to copy any SQLServer dependencies, such as logon
accounts. After that, you can use a log shipping solution to
syncronize the two istances. There are some alternatives like execute
a copy database or a database mirroring solution or detach/attach the
database files.
When the new istance will be sincronized and your tests on it will be
positive, you can switch to the new cluster and then reconnect
apllications.

Regards
Riccardo

You may start with creation of a new sqlserver2005 cluster instance
with its own new resources.
You will then need to copy any SQLServer dependencies, such as logon
accounts. After that, you can use a log shipping solution to
syncronize the two istances. There are some alternatives like execute
a copy database or a database mirroring solution or detach/attach the
database files.
When the new istance will be sincronized and your tests on it will be
positive, you can switch to the new cluster and then reconnect
apllications.

Regards
Riccardo

You may start with creation of a new sqlserver2005 cluster instance
with its own new resources.
You will then need to copy any SQLServer dependencies, such as logon
accounts. After that, you can use a log shipping solution to
syncronize the two istances. There are some alternatives like execute
a copy database or a database mirroring solution or detach/attach the
database files.
When the new istance will be sincronized and your tests on it will be
positive, you can switch to the new cluster and then reconnect
apllications.

Regards
Riccardo