I have:
-nt 4 enterprise w/ sp6a
-MSCS Active/Passive
-sql 7.x enterprise w/ sp3
I want to upg the SQL 7 to SQL 2000.
Do I:
-Upgrade server 1 to sql 2000, then move the group to
server 2 and upg it?
thank you
Hello,
Refer to the following articles in SQL Server 2000 Books Online. The latest
version of SQL Server 2000 Books Online can be downloaded from the
following link
http://www.microsoft.com/sql/techinf...2000/books.asp
How to upgrade from a SQL Server 7.0 active/passive failover cluster (Setup)
How to upgrade from a SQL Server 7.0 active/active failover cluster (Setup)
How to upgrade from a default instance to a default clustered instance of
SQL Server 2000 (SQL Server Setup).
To upgrade from a SQL Server 7.0 active/passive failover cluster
1)On Node 1, uncluster Microsoft SQL Server version 7.0. Reboot Node 1.
2)On Node 1, upgrade SQL Server 7.0 to SQL Server 2000 as the default
instance.
You must install the binaries to a local drive and use a cluster disk for
the data. This local drive is a path, which is a non-clustered disk valid
on all nodes of the cluster. This drive on all nodes of the cluster must
have at least 300 megabytes (MB) of available space.
3)On Node 1, upgrade the default instance of SQL Server 2000 to a clustered
instance of SQL Server 2000.
For more information, see How to upgrade from a default instance to a
default clustered instance of SQL Server 2000 (SQL Server Setup).
Thanks
Deepali
This posting is provided "AS IS" with no warranties, and confers no rights
|||Ok...
First I un cluster
second, do the upgrade,
third, upg to a clustered sql 2k...
This should take care of node2 as well?
>--Original Message--
>Hello,
>Refer to the following articles in SQL Server 2000 Books=20
Online. The latest=20
>version of SQL Server 2000 Books Online can be downloaded=20
from the=20
>following link
>http://www.microsoft.com/sql/techinf...tdoc/2000/book
s.asp
>How to upgrade from a SQL Server 7.0 active/passive=20
failover cluster (Setup)
>How to upgrade from a SQL Server 7.0 active/active=20
failover cluster (Setup)
>How to upgrade from a default instance to a default=20
clustered instance of=20
>SQL Server 2000 (SQL Server Setup).
>To upgrade from a SQL Server 7.0 active/passive failover=20
cluster=20
>1)On Node 1, uncluster Microsoft=AE SQL ServerT version=20
7.0. Reboot Node 1.
>2)On Node 1, upgrade SQL Server 7.0 to SQL Server 2000 as=20
the default=20
>instance.=20
>You must install the binaries to a local drive and use a=20
cluster disk for=20
>the data. This local drive is a path, which is a non-
clustered disk valid=20
>on all nodes of the cluster. This drive on all nodes of=20
the cluster must=20
>have at least 300 megabytes (MB) of available space.
>3)On Node 1, upgrade the default instance of SQL Server=20
2000 to a clustered=20
>instance of SQL Server 2000.=20
>For more information, see How to upgrade from a default=20
instance to a=20
>default clustered instance of SQL Server 2000 (SQL Server=20
Setup).
>
>Thanks
>Deepali
>This posting is provided "AS IS" with no warranties, and=20
confers no rights
>.
>
|||what happens to cluster 2?
[vbcol=seagreen]
>--Original Message--
>Ok...
>First I un cluster
>second, do the upgrade,
>third, upg to a clustered sql 2k...
>This should take care of node2 as well?
>
>
>Online. The latest=20
downloaded=20[vbcol=seagreen]
>from the=20
k[vbcol=seagreen]
>s.asp
>failover cluster (Setup)
>failover cluster (Setup)
>clustered instance of=20
>cluster=20
>7.0. Reboot Node 1.
as=20[vbcol=seagreen]
>the default=20
>cluster disk for=20
>clustered disk valid=20
>the cluster must=20
>2000 to a clustered=20
>instance to a=20
Server=20
>Setup).
>confers no rights
>.
>
|||SQL Server 2000 setup is cluster aware. When you run SQL Server 2000 setup. When you run the SQL 2000 setup for installing clustered instance, it will automatically copy all the required binaries on the other nodes
of the cluster.
Additional Information
Microsoft Whitepaper - SQL Server 2000 Failover Clustering
http://www.microsoft.com/SQL/techinf...vercluster.asp
SQL Server 2000 Pricing and Licensing
http://www.microsoft.com/sql/howtobu...rlicensing.asp
Microsoft SQL Server 2000 High Availability Series
http://www.microsoft.com/technet/pro...y/sqlhalp.mspx
Microsoft Webcasts
Introduction to Microsoft SQL Server 2000 Clustering
http://support.microsoft.com/default...lurb051001.asp
Microsoft SQL Server 2000 Virtual Server: Things You Should Know
http://support.microsoft.com/default...lurb032602.asp
Microsoft SQL Server 2000 Virtual Server Basic Setup, Maintenance, and Service Pack
http://support.microsoft.com/default...lurb061002.asp
Microsoft SQL Server 2000 Failover Clustering Disaster Recovery Procedures
http://support.microsoft.com/default...lurb101802.asp
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default...lurb020703.asp
Q243218 INF: Installation Order for SQL 2000 Enterprise Edition
http://support.microsoft.com/?kbid=243218
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
sql
Showing posts with label upg. Show all posts
Showing posts with label upg. Show all posts
Thursday, March 22, 2012
Thursday, March 8, 2012
act/pass cluster upg from geerhead...
following up on the geerhead message:
first, uncluster the SQL then reboot node1
second, upg the sql 7 to sql 2000
third, upg the sql 2k to sql 2000 cluster instance...
OK...are there any upgrades to node2? Or will thw sql 2k
cluster instance take care of that?
The upgrade from a standalone to a clustered instance will apply the RTM
version of the SQL Server files to any nodes listed as possible owners. So
you have to then reapply the latest service pack and any hotfixes (see the
readme for sp3a).
Note that you can only upgrade from standalone to clustered if the binaries
are on the local drives and the data is all on one or more shared drives.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||So, if I have all the programs and data and the quorum on
a shared drive, this should be ok?
>--Original Message--
>The upgrade from a standalone to a clustered instance
will apply the RTM
>version of the SQL Server files to any nodes listed as
possible owners. So
>you have to then reapply the latest service pack and any
hotfixes (see the
>readme for sp3a).
>Note that you can only upgrade from standalone to
clustered if the binaries
>are on the local drives and the data is all on one or
more shared drives.
>Cindy Gross, MCDBA, MCSE
>http://cindygross.tripod.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>.
>
|||No and No. First, SQL should not share a physical disk resource with teh
quorum drive. This defeats the entire high availability strategy of
clustering. Second, SQL operates on local binaries and shared data.
Binaries (Programs) need to be on local disks. The installer will handle
installing/updating all cluster nodes at once.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"geerhead" <anonymous@.discussions.microsoft.com> wrote in message
news:607701c42e09$ac9bede0$a601280a@.phx.gbl...[vbcol=seagreen]
> So, if I have all the programs and data and the quorum on
> a shared drive, this should be ok?
>
>
> will apply the RTM
> possible owners. So
> hotfixes (see the
> clustered if the binaries
> more shared drives.
> confers no rights.
|||The binaries are separated. You can put data on the same drive as the
quorum. It isn't recommended, but it can be done without any side effects
to the cluster.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
first, uncluster the SQL then reboot node1
second, upg the sql 7 to sql 2000
third, upg the sql 2k to sql 2000 cluster instance...
OK...are there any upgrades to node2? Or will thw sql 2k
cluster instance take care of that?
The upgrade from a standalone to a clustered instance will apply the RTM
version of the SQL Server files to any nodes listed as possible owners. So
you have to then reapply the latest service pack and any hotfixes (see the
readme for sp3a).
Note that you can only upgrade from standalone to clustered if the binaries
are on the local drives and the data is all on one or more shared drives.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||So, if I have all the programs and data and the quorum on
a shared drive, this should be ok?
>--Original Message--
>The upgrade from a standalone to a clustered instance
will apply the RTM
>version of the SQL Server files to any nodes listed as
possible owners. So
>you have to then reapply the latest service pack and any
hotfixes (see the
>readme for sp3a).
>Note that you can only upgrade from standalone to
clustered if the binaries
>are on the local drives and the data is all on one or
more shared drives.
>Cindy Gross, MCDBA, MCSE
>http://cindygross.tripod.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>.
>
|||No and No. First, SQL should not share a physical disk resource with teh
quorum drive. This defeats the entire high availability strategy of
clustering. Second, SQL operates on local binaries and shared data.
Binaries (Programs) need to be on local disks. The installer will handle
installing/updating all cluster nodes at once.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"geerhead" <anonymous@.discussions.microsoft.com> wrote in message
news:607701c42e09$ac9bede0$a601280a@.phx.gbl...[vbcol=seagreen]
> So, if I have all the programs and data and the quorum on
> a shared drive, this should be ok?
>
>
> will apply the RTM
> possible owners. So
> hotfixes (see the
> clustered if the binaries
> more shared drives.
> confers no rights.
|||The binaries are separated. You can put data on the same drive as the
quorum. It isn't recommended, but it can be done without any side effects
to the cluster.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
Subscribe to:
Posts (Atom)