SQL 2k to SQL 2K5 in Active Passive Cluster

#1

We are going for SQL 2K Upgrade to SQL 2k5 Upgrade for Active-Passive
Clusters (windows 2K3)and thinking for below plan , can anybody confirm if we
are ignoring or missing big issues with below plan or it sounds good?

o Put SQL 2005 on one server
o Leave SQL 2000 on the other
o Virtual name of the cluster will remain pointed at the SQL 2000 server
o New Build will be tested on the SQL 2005 server
o If the new software fails, we still have everything working on the SQL
2000 server
o When the SQL 2005 server is ready with Build and tested , the SQL 2000
server is turned off and virtual name of the cluster is pointed at the SQL
2005 server.
• Also if there is no issue you see , what is the process to point to point
the virtual name from SQL 2K to SQL 2K5

Thanks

#2

Based on your description, are you trying to upgrade an existing SQL Server
2000 single instance cluster to SQL Server 2005 or are you trying to migrate
your SQL Server data from a SQL Server 2000 system to a SQL Server 2005
clustered system?

If you are trying to upgrade a SQL Server cluster from SQL 2000 to SQL
Server 2005 follow these steps SQL Server 2005 Failover Clustering White
Paper:

http://thesource.ofallevil.com/downl...displayLang=en

Side by side installation with SQL Server 2000 Failover Clusters

Thanks

Ross Mistry

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

Quote:

We are going for SQL 2K Upgrade to SQL 2k5 Upgrade for Active-Passive
Clusters (windows 2K3)and thinking for below plan , can anybody confirm if
we
are ignoring or missing big issues with below plan or it sounds good?

o Put SQL 2005 on one server
o Leave SQL 2000 on the other
o Virtual name of the cluster will remain pointed at the SQL 2000 server
o New Build will be tested on the SQL 2005 server
o If the new software fails, we still have everything working on the SQL
2000 server
o When the SQL 2005 server is ready with Build and tested , the SQL 2000
server is turned off and virtual name of the cluster is pointed at the SQL
2005 server.
. Also if there is no issue you see , what is the process to point to
point
the virtual name from SQL 2K to SQL 2K5

Thanks

#3

Based on your description, are you trying to upgrade an existing SQL Server
2000 single instance cluster to SQL Server 2005 or are you trying to migrate
your SQL Server data from a SQL Server 2000 system to a SQL Server 2005
clustered system?

If you are trying to upgrade a SQL Server cluster from SQL 2000 to SQL
Server 2005 follow these steps SQL Server 2005 Failover Clustering White
Paper:

http://thesource.ofallevil.com/downl...displayLang=en

Side by side installation with SQL Server 2000 Failover Clusters

Thanks

Ross Mistry

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

Quote:

We are going for SQL 2K Upgrade to SQL 2k5 Upgrade for Active-Passive
Clusters (windows 2K3)and thinking for below plan , can anybody confirm if
we
are ignoring or missing big issues with below plan or it sounds good?

o Put SQL 2005 on one server
o Leave SQL 2000 on the other
o Virtual name of the cluster will remain pointed at the SQL 2000 server
o New Build will be tested on the SQL 2005 server
o If the new software fails, we still have everything working on the SQL
2000 server
o When the SQL 2005 server is ready with Build and tested , the SQL 2000
server is turned off and virtual name of the cluster is pointed at the SQL
2005 server.
. Also if there is no issue you see , what is the process to point to
point
the virtual name from SQL 2K to SQL 2K5

Thanks

#4

Based on your description, are you trying to upgrade an existing SQL Server
2000 single instance cluster to SQL Server 2005 or are you trying to migrate
your SQL Server data from a SQL Server 2000 system to a SQL Server 2005
clustered system?

If you are trying to upgrade a SQL Server cluster from SQL 2000 to SQL
Server 2005 follow these steps SQL Server 2005 Failover Clustering White
Paper:

http://thesource.ofallevil.com/downl...displayLang=en

Side by side installation with SQL Server 2000 Failover Clusters

Thanks

Ross Mistry

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

Quote:

We are going for SQL 2K Upgrade to SQL 2k5 Upgrade for Active-Passive
Clusters (windows 2K3)and thinking for below plan , can anybody confirm if
we
are ignoring or missing big issues with below plan or it sounds good?

o Put SQL 2005 on one server
o Leave SQL 2000 on the other
o Virtual name of the cluster will remain pointed at the SQL 2000 server
o New Build will be tested on the SQL 2005 server
o If the new software fails, we still have everything working on the SQL
2000 server
o When the SQL 2005 server is ready with Build and tested , the SQL 2000
server is turned off and virtual name of the cluster is pointed at the SQL
2005 server.
. Also if there is no issue you see , what is the process to point to
point
the virtual name from SQL 2K to SQL 2K5

Thanks

#5

Based on your description, are you trying to upgrade an existing SQL Server
2000 single instance cluster to SQL Server 2005 or are you trying to migrate
your SQL Server data from a SQL Server 2000 system to a SQL Server 2005
clustered system?

If you are trying to upgrade a SQL Server cluster from SQL 2000 to SQL
Server 2005 follow these steps SQL Server 2005 Failover Clustering White
Paper:

http://thesource.ofallevil.com/downl...displayLang=en

Side by side installation with SQL Server 2000 Failover Clusters

Thanks

Ross Mistry

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

Quote:

We are going for SQL 2K Upgrade to SQL 2k5 Upgrade for Active-Passive
Clusters (windows 2K3)and thinking for below plan , can anybody confirm if
we
are ignoring or missing big issues with below plan or it sounds good?

o Put SQL 2005 on one server
o Leave SQL 2000 on the other
o Virtual name of the cluster will remain pointed at the SQL 2000 server
o New Build will be tested on the SQL 2005 server
o If the new software fails, we still have everything working on the SQL
2000 server
o When the SQL 2005 server is ready with Build and tested , the SQL 2000
server is turned off and virtual name of the cluster is pointed at the SQL
2005 server.
. Also if there is no issue you see , what is the process to point to
point
the virtual name from SQL 2K to SQL 2K5

Thanks

#6

Based on your description, are you trying to upgrade an existing SQL Server
2000 single instance cluster to SQL Server 2005 or are you trying to migrate
your SQL Server data from a SQL Server 2000 system to a SQL Server 2005
clustered system?

If you are trying to upgrade a SQL Server cluster from SQL 2000 to SQL
Server 2005 follow these steps SQL Server 2005 Failover Clustering White
Paper:

http://thesource.ofallevil.com/downl...displayLang=en

Side by side installation with SQL Server 2000 Failover Clusters

Thanks

Ross Mistry

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

Quote:

We are going for SQL 2K Upgrade to SQL 2k5 Upgrade for Active-Passive
Clusters (windows 2K3)and thinking for below plan , can anybody confirm if
we
are ignoring or missing big issues with below plan or it sounds good?

o Put SQL 2005 on one server
o Leave SQL 2000 on the other
o Virtual name of the cluster will remain pointed at the SQL 2000 server
o New Build will be tested on the SQL 2005 server
o If the new software fails, we still have everything working on the SQL
2000 server
o When the SQL 2005 server is ready with Build and tested , the SQL 2000
server is turned off and virtual name of the cluster is pointed at the SQL
2005 server.
. Also if there is no issue you see , what is the process to point to
point
the virtual name from SQL 2K to SQL 2K5

Thanks

#7

Based on your description, are you trying to upgrade an existing SQL Server
2000 single instance cluster to SQL Server 2005 or are you trying to migrate
your SQL Server data from a SQL Server 2000 system to a SQL Server 2005
clustered system?

If you are trying to upgrade a SQL Server cluster from SQL 2000 to SQL
Server 2005 follow these steps SQL Server 2005 Failover Clustering White
Paper:

http://thesource.ofallevil.com/downl...displayLang=en

Side by side installation with SQL Server 2000 Failover Clusters

Thanks

Ross Mistry

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

Quote:

We are going for SQL 2K Upgrade to SQL 2k5 Upgrade for Active-Passive
Clusters (windows 2K3)and thinking for below plan , can anybody confirm if
we
are ignoring or missing big issues with below plan or it sounds good?

o Put SQL 2005 on one server
o Leave SQL 2000 on the other
o Virtual name of the cluster will remain pointed at the SQL 2000 server
o New Build will be tested on the SQL 2005 server
o If the new software fails, we still have everything working on the SQL
2000 server
o When the SQL 2005 server is ready with Build and tested , the SQL 2000
server is turned off and virtual name of the cluster is pointed at the SQL
2005 server.
. Also if there is no issue you see , what is the process to point to
point
the virtual name from SQL 2K to SQL 2K5

Thanks

#8

Based on your description, are you trying to upgrade an existing SQL Server
2000 single instance cluster to SQL Server 2005 or are you trying to migrate
your SQL Server data from a SQL Server 2000 system to a SQL Server 2005
clustered system?

If you are trying to upgrade a SQL Server cluster from SQL 2000 to SQL
Server 2005 follow these steps SQL Server 2005 Failover Clustering White
Paper:

http://thesource.ofallevil.com/downl...displayLang=en

Side by side installation with SQL Server 2000 Failover Clusters

Thanks

Ross Mistry

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

Quote:

We are going for SQL 2K Upgrade to SQL 2k5 Upgrade for Active-Passive
Clusters (windows 2K3)and thinking for below plan , can anybody confirm if
we
are ignoring or missing big issues with below plan or it sounds good?

o Put SQL 2005 on one server
o Leave SQL 2000 on the other
o Virtual name of the cluster will remain pointed at the SQL 2000 server
o New Build will be tested on the SQL 2005 server
o If the new software fails, we still have everything working on the SQL
2000 server
o When the SQL 2005 server is ready with Build and tested , the SQL 2000
server is turned off and virtual name of the cluster is pointed at the SQL
2005 server.
. Also if there is no issue you see , what is the process to point to
point
the virtual name from SQL 2K to SQL 2K5

Thanks

#9

Based on your description, are you trying to upgrade an existing SQL Server
2000 single instance cluster to SQL Server 2005 or are you trying to migrate
your SQL Server data from a SQL Server 2000 system to a SQL Server 2005
clustered system?

If you are trying to upgrade a SQL Server cluster from SQL 2000 to SQL
Server 2005 follow these steps SQL Server 2005 Failover Clustering White
Paper:

http://thesource.ofallevil.com/downl...displayLang=en

Side by side installation with SQL Server 2000 Failover Clusters

Thanks

Ross Mistry

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

Quote:

We are going for SQL 2K Upgrade to SQL 2k5 Upgrade for Active-Passive
Clusters (windows 2K3)and thinking for below plan , can anybody confirm if
we
are ignoring or missing big issues with below plan or it sounds good?

o Put SQL 2005 on one server
o Leave SQL 2000 on the other
o Virtual name of the cluster will remain pointed at the SQL 2000 server
o New Build will be tested on the SQL 2005 server
o If the new software fails, we still have everything working on the SQL
2000 server
o When the SQL 2005 server is ready with Build and tested , the SQL 2000
server is turned off and virtual name of the cluster is pointed at the SQL
2005 server.
. Also if there is no issue you see , what is the process to point to
point
the virtual name from SQL 2K to SQL 2K5

Thanks

#10

Based on your description, are you trying to upgrade an existing SQL Server
2000 single instance cluster to SQL Server 2005 or are you trying to migrate
your SQL Server data from a SQL Server 2000 system to a SQL Server 2005
clustered system?

If you are trying to upgrade a SQL Server cluster from SQL 2000 to SQL
Server 2005 follow these steps SQL Server 2005 Failover Clustering White
Paper:

http://thesource.ofallevil.com/downl...displayLang=en

Side by side installation with SQL Server 2000 Failover Clusters

Thanks

Ross Mistry

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

Quote:

We are going for SQL 2K Upgrade to SQL 2k5 Upgrade for Active-Passive
Clusters (windows 2K3)and thinking for below plan , can anybody confirm if
we
are ignoring or missing big issues with below plan or it sounds good?

o Put SQL 2005 on one server
o Leave SQL 2000 on the other
o Virtual name of the cluster will remain pointed at the SQL 2000 server
o New Build will be tested on the SQL 2005 server
o If the new software fails, we still have everything working on the SQL
2000 server
o When the SQL 2005 server is ready with Build and tested , the SQL 2000
server is turned off and virtual name of the cluster is pointed at the SQL
2005 server.
. Also if there is no issue you see , what is the process to point to
point
the virtual name from SQL 2K to SQL 2K5

Thanks