"Geoff N. Hiten" wrote:
> Each instance has its own set of binaries so each instance can be a
> different version.
>
> Binaries are updated cluster-wide for a specific instance during a SP,
> hotfix, or version upgrade transparently during the install.
>
> Here is the documentation on what is and is not supported in mixed-version
> clusters:
>
> The Microsoft SQL Server support policy for Microsoft Clustering
>
http://support.microsoft.com/kb/327518/en-us >
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
>
> "ctowndu33" <ctowndu33@discussions.microsoft.com> wrote in message
> news:8C1F58A9-294E-4748-A2B6-7D5B6DB9ADA7@microsoft.com...
> > When you upgrade the one instance, doesn't that upgrade the sql files on
> > the
> > actual physical node so that when you fail the 2000 instance over, it will
> > not work? I guess my question is what files for sql reside on the
> > physical
> > cluster node that would get upgraded that would inhibit a 2000 virtual
> > group
> > from running on it. When upgrading to sql 2k5, does it only affect files
> > that are contained in the virtual group? Thanks in advance!
> >
> > "Tom Moreau" wrote:
> >
> >> You can upgrade one instance at a time. Thus, you can have one SQL2K
> >> instance and another SQL2005 instance on the same cluster after the
> >> upgrade.
> >>
> >> --
> >> Tom
> >>
> >> ----------------------------------------------------
> >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> >> SQL Server MVP
> >> Toronto, ON Canada
> >> ..
> >> "ctowndu33" <ctowndu33@discussions.microsoft.com> wrote in message
> >> news:C6771D1E-26C3-4544-8A1F-74C8BF1573D3@microsoft.com...
> >> We have a two node cluster with two groups on them (W2K3). Each group
> >> has a
> >> sql 2k instance running and the groups each reside on a node, failing
> >> over
> >> to
> >> the other if necessary. My question is that we were looking to upgrade,
> >> but
> >> are only able to upgrade the one instance to 2K5. I assume this would
> >> break
> >> our failover for the sql 2K cluster group since it would be on a node
> >> that
> >> has been upgraded to 2K5?
> >>
> >>
>