Re: SQL 2k to SQL 2K5 in Active Passive Cluster

Tech-Archive recommends: Fix windows errors by optimizing your registry

Great, so do you mean

1) Install SQL 2k5 cluster instance
2) Test everything with instance name
3) if everything goes fine map the DNS of default 2K cluster to new 2K5
cluster
4) Uninstall 2K cluster

if above is the case then it looks better plan ,but how i will manage the
LUNs which are already part of current SQL 2K(binaries on H$ shared drive)
what are the precautions and action point i need to take for LUNs and while
un-installing the sql2k cluster?

Thanks much..






"Geoff N. Hiten" wrote:

I do not think this will work.

The SQL 2005 installer treats the clustered instance singly for update
purposes. The installer will exit if any cluster resource is offline, so
you cannot "reserve" one node to failback. Also, once a database file is
upgraded to SQL 2005, it cannot be attached to a SQL 2000 instance.

I would recommend a side-by-side installation of a named instance of SQl
2005. You can then do a data-in-place migration after you have tested
everything. A DNS SRV record can point the old virtual server name to the
new named instance so you do not have to try and rename a clustered
instance.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP



"sacgar" <sacgar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:02F601FA-749E-4AE7-8011-D1CF8AC133E4@xxxxxxxxxxxxxxxx

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


.

Relevant Pages

  • Re: N+1 Configuration
    ... Jasper Smith (SQL Server MVP) ... But looking in the cluster admin tool, ... mounting all other drives under that drive ...
    (microsoft.public.sqlserver.clustering)
  • Re: Clustering Question
    ... I have worked with Windows 2003 Small Business Server, Exchange Server 2003 and 2000 SQL server but not in a clustered environment. ... Do you want to cluster SQL? ... > you cannot install Cluster on a Small Business Edition, ...
    (microsoft.public.windows.server.clustering)
  • Re: Clustering Question
    ... The SQL Cluster would need to be ... SQL will need to Enterprise as well. ... So if I understand you correctly one computer will need Windows Server ...
    (microsoft.public.windows.server.clustering)
  • Re: Issues creating a new failover cluster on the same server
    ... G:\Microsoft SQL Server\MSSQL.1 ... CHNSQL04 Cluster Group ... Drives: H and F ... Group, the MS DTC Group, and each of the SQL Server Instance Groups running ...
    (microsoft.public.sqlserver.clustering)
  • Re: Connecting to cluster instance from .NET
    ... I have tried using the SQL 2000 CD and i have ... Virtual IP addresses for the cluster resource groups. ... SQL Server will listen on only those IP addresses ... This is odd because the 172.16 network is a Class B ...
    (microsoft.public.sqlserver.clustering)