Applying SP4 on an active/passive 2 way cluster

I have a 2 way cluster and I want to apply SP4 on it.
Basically, I have 2 servers. Server A runs a default instance and
another instance. While the default services is disabled and the other
instance is running, Server B runs the default instance and has the other
instance disabled. This basically acts like a 2 way cluster
(active/passive).
How can I apply SQL Server 2000 SP4 on the 2 servers and have all the
nodes come up the correct way? What are the steps to achieve this?http://download.microsoft.com/download/1/B/D/1BDF5B78-584E-4DE0-B36F-
C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||This is not going to help me. I have explicitly mentioned that I have a 2
way cluster in my original email. So a standard article like you have given
me is NOT going to help.
"Ole Kristian Bangås" <olekristian.bangas@.masterminds.no> wrote in message
news:Xns981DB671F914Folekristianbangaas@.207.46.248.16...
> http://download.microsoft.com/download/1/B/D/1BDF5B78-584E-4DE0-B36F-
> C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
> --
> Ole Kristian Bangås
> MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
> This is not going to help me. I have explicitly mentioned that I have
> a 2 way cluster in my original email. So a standard article like you
> have given me is NOT going to help.
Yes, and I don't quite get the problem. Let me quote point two in the
article I gave a link to:
"Run the service pack from the node that owns the group containing the
virtual server that you plan to upgrade. This installs the service pack
files on all nodes in the failover cluster."
Can you please explain what your problem is? As I understand your scenario
you have a two-node two-instance active-passive SQL cluster. An upgrade of
that cluster should be rather straightforward.
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
Correction to my previous post, You actually have an active/active
confuguration, with one instance on each server, but the upgrade procedure
is still valid.
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP

Applying SP4 on an active/passive 2 way cluster

I have a 2 way cluster and I want to apply SP4 on it.

Basically, I have 2 servers. Server A runs a default instance and another instance. While the default services is disabled and the other instance is running, Server B runs the default instance and has the other instance disabled. This basically acts like a 2 way cluster (active/passive).

How can I apply SQL Server 2000 SP4 on the 2 servers and have all the nodes come up the correct way? What are the steps to achieve this?Since SQL Server is a shared resource on a clustered server, installing SP4 on one server is automatically done on the other. Everything is transparent to the user/admin.sql

Applying SP4 on an active/passive 2 way cluster

I have a 2 way cluster and I want to apply SP4 on it.
Basically, I have 2 servers. Server A runs a default instance and
another instance. While the default services is disabled and the other
instance is running, Server B runs the default instance and has the other
instance disabled. This basically acts like a 2 way cluster
(active/passive).
How can I apply SQL Server 2000 SP4 on the 2 servers and have all the
nodes come up the correct way? What are the steps to achieve this?http://download.microsoft.com/downl...584E-4DE0-B36F-
C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||This is not going to help me. I have explicitly mentioned that I have a 2
way cluster in my original email. So a standard article like you have given
me is NOT going to help.
"Ole Kristian Bangs" <olekristian.bangas@.masterminds.no> wrote in message
news:Xns981DB671F914Folekristianbangaas@.
207.46.248.16...
> http://download.microsoft.com/downl...584E-4DE0-B36F-
> C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
> --
> Ole Kristian Bangs
> MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:

> This is not going to help me. I have explicitly mentioned that I have
> a 2 way cluster in my original email. So a standard article like you
> have given me is NOT going to help.
Yes, and I don't quite get the problem. Let me quote point two in the
article I gave a link to:
"Run the service pack from the node that owns the group containing the
virtual server that you plan to upgrade. This installs the service pack
files on all nodes in the failover cluster."
Can you please explain what your problem is? As I understand your scenario
you have a two-node two-instance active-passive SQL cluster. An upgrade of
that cluster should be rather straightforward.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
Correction to my previous post, You actually have an active/active
confuguration, with one instance on each server, but the upgrade procedure
is still valid.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP

applying SP to 2005 active/active cluster

I have a 2005 active/active cluster and want to apply SQL server 2005 SP2 to both node.
I know that for active/passive , the sp can simple be installed on the active node(instance) and everything will be replicated to the other node.
bear in mind what I have SSIS and SSAS and SSRS running on the active/active cluster.

what is the rigth method for applying the SP to active\active cluster?

Thanks

We had the same situation a couple of weeks ago. When had several problems applying SP2 to the clustered machines. After talking to MS for several hrs about our problems, we finally corrected it....it was issues with different settings on our cluster. However, MS did recommend having both instances on one server, the primary, when you do the upgrade. I can't remember if the SP was applied to both nodes though. If it is not, its no big deal. Just apply it to the second node. I hope you have better luck than we did.

PS. Make sure that DCOM is enabled on both servers.

Applying SP on SQL Cluster (active/passive) after new nodes Added

Ran into a problem in scheduling applying the Service Pack to our SQL
2000 active/passive cluster when we add new nodes. 50 plus databases and an
unknown number of apps.
I'm wondering what people do to ensure that no apps/people are trying to
access the databases when the service pack is applied.
Our application staff says there is no way they can guarantee that an
app or person will not try to access one of the databases while the service
pack is being installed.
My plan is to evict one of the existing nodes then add the two new nodes
one at a time and set up the heartbeat. Then install SQL 2000; then apply
SP3a. Yes I know SP4 is available; however, one of the apps will not run
with SP4.
The service pack brings the database engine up in single-user mode during
the SP install. Unless your applications are connecting as SA or
equivalent, there should be no conflict.
If the apps are connecting as SA, change the password before applying the SP
and change it back when you are done. Then fix that glaring security and
managability hole.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Pat Hall" <PatHall@.discussions.microsoft.com> wrote in message
news:FA6E93F9-78FC-497E-A4F0-E4D459F85CA9@.microsoft.com...
> Ran into a problem in scheduling applying the Service Pack to our SQL
> 2000 active/passive cluster when we add new nodes. 50 plus databases and
> an
> unknown number of apps.
> I'm wondering what people do to ensure that no apps/people are trying
> to
> access the databases when the service pack is applied.
> Our application staff says there is no way they can guarantee that an
> app or person will not try to access one of the databases while the
> service
> pack is being installed.
> My plan is to evict one of the existing nodes then add the two new
> nodes
> one at a time and set up the heartbeat. Then install SQL 2000; then
> apply
> SP3a. Yes I know SP4 is available; however, one of the apps will not run
> with SP4.
|||I thought in single-user mode, that any ID could be used and the 1st one
wins. SA or not. I also thought that the service pack brings the database
engine up and down several times while it is applying the service pack.
The other restriction (db_owner, sysadmin, bd_creator) isn't an option for
us either since many of the app IDs are db_owner in their database.
"Geoff N. Hiten" wrote:

> The service pack brings the database engine up in single-user mode during
> the SP install. Unless your applications are connecting as SA or
> equivalent, there should be no conflict.
>
> If the apps are connecting as SA, change the password before applying the SP
> and change it back when you are done. Then fix that glaring security and
> managability hole.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Pat Hall" <PatHall@.discussions.microsoft.com> wrote in message
> news:FA6E93F9-78FC-497E-A4F0-E4D459F85CA9@.microsoft.com...
>
|||There is single-user mode for a database, and then there is single-user mode
for the entire database service. The SP starts the entire service in
single-user mode and immediately claims the connection.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Pat Hall" <PatHall@.discussions.microsoft.com> wrote in message
news:98107803-0953-4B12-986E-FB82CDCBA45B@.microsoft.com...[vbcol=seagreen]
>I thought in single-user mode, that any ID could be used and the 1st one
> wins. SA or not. I also thought that the service pack brings the
> database
> engine up and down several times while it is applying the service pack.
> The other restriction (db_owner, sysadmin, bd_creator) isn't an option for
> us either since many of the app IDs are db_owner in their database.
> "Geoff N. Hiten" wrote:
|||Thanks. So do I even need to get all the apps down before I start applying
a service pack? I would think so, so they close out of what they are doing
in an orderly fashion. Just not worry about them trying to get in while the
service pack is running.
"Geoff N. Hiten" wrote:

> There is single-user mode for a database, and then there is single-user mode
> for the entire database service. The SP starts the entire service in
> single-user mode and immediately claims the connection.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Pat Hall" <PatHall@.discussions.microsoft.com> wrote in message
> news:98107803-0953-4B12-986E-FB82CDCBA45B@.microsoft.com...
>
|||You need a standard practice for maintenance, regardless of whether you are
applying a hotfix or an internal update. This includes procedures for
stopping and starting the entire system.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Pat Hall" <PatHall@.discussions.microsoft.com> wrote in message
news:D497CBD2-637D-490C-9BAD-6AA49F145000@.microsoft.com...[vbcol=seagreen]
> Thanks. So do I even need to get all the apps down before I start
> applying
> a service pack? I would think so, so they close out of what they are
> doing
> in an orderly fashion. Just not worry about them trying to get in while
> the
> service pack is running.
> "Geoff N. Hiten" wrote:

Applying 2003 SP1 to a SQL Cluster running SP3

Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
issues that we want to wait.We did just this on Saturday and it has been a nightmare. Everything was
running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
wreaked havoc!
Our overall performance has dropped dramatically. What used to take 2
seconds to run now takes upwards of 6. We've been working with Microsoft an
d
they have absolutely no idea what the problem is and haven't really offered
much in terms of troubleshooting ideas either.
One suggestion we've heard is to update statictics on all tables (which I am
doing right now) but it doesn't seem to make a difference.
Of course Microsoft says that all of this should work fine and that W2K3 SP1
and SQL 2000 SP3 should co-exist fine in a cluster...
Good luck!
"JGTKD" wrote:

> Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQ
L
> Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
> issues that we want to wait.|||Any updates on this thread? I am looking to do the same thing (sp1 on 2003
Enterprise Server running mssql2000 sp3) in the near future.
Thanks.
"Drinian" wrote:
[vbcol=seagreen]
> We did just this on Saturday and it has been a nightmare. Everything was
> running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
> wreaked havoc!
> Our overall performance has dropped dramatically. What used to take 2
> seconds to run now takes upwards of 6. We've been working with Microsoft
and
> they have absolutely no idea what the problem is and haven't really offere
d
> much in terms of troubleshooting ideas either.
> One suggestion we've heard is to update statictics on all tables (which I
am
> doing right now) but it doesn't seem to make a difference.
> Of course Microsoft says that all of this should work fine and that W2K3 S
P1
> and SQL 2000 SP3 should co-exist fine in a cluster...
> Good luck!
> "JGTKD" wrote:
>

Applying 2003 SP1 to a SQL Cluster running SP3

Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
issues that we want to wait.
We did just this on Saturday and it has been a nightmare. Everything was
running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
wreaked havoc!
Our overall performance has dropped dramatically. What used to take 2
seconds to run now takes upwards of 6. We've been working with Microsoft and
they have absolutely no idea what the problem is and haven't really offered
much in terms of troubleshooting ideas either.
One suggestion we've heard is to update statictics on all tables (which I am
doing right now) but it doesn't seem to make a difference.
Of course Microsoft says that all of this should work fine and that W2K3 SP1
and SQL 2000 SP3 should co-exist fine in a cluster...
Good luck!
"JGTKD" wrote:

> Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
> Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
> issues that we want to wait.
|||Any updates on this thread? I am looking to do the same thing (sp1 on 2003
Enterprise Server running mssql2000 sp3) in the near future.
Thanks.
"Drinian" wrote:
[vbcol=seagreen]
> We did just this on Saturday and it has been a nightmare. Everything was
> running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
> wreaked havoc!
> Our overall performance has dropped dramatically. What used to take 2
> seconds to run now takes upwards of 6. We've been working with Microsoft and
> they have absolutely no idea what the problem is and haven't really offered
> much in terms of troubleshooting ideas either.
> One suggestion we've heard is to update statictics on all tables (which I am
> doing right now) but it doesn't seem to make a difference.
> Of course Microsoft says that all of this should work fine and that W2K3 SP1
> and SQL 2000 SP3 should co-exist fine in a cluster...
> Good luck!
> "JGTKD" wrote:

Applying 2003 SP1 to a SQL Cluster running SP3

Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
issues that we want to wait.We did just this on Saturday and it has been a nightmare. Everything was
running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
wreaked havoc!
Our overall performance has dropped dramatically. What used to take 2
seconds to run now takes upwards of 6. We've been working with Microsoft and
they have absolutely no idea what the problem is and haven't really offered
much in terms of troubleshooting ideas either.
One suggestion we've heard is to update statictics on all tables (which I am
doing right now) but it doesn't seem to make a difference.
Of course Microsoft says that all of this should work fine and that W2K3 SP1
and SQL 2000 SP3 should co-exist fine in a cluster...
Good luck!
"JGTKD" wrote:
> Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
> Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
> issues that we want to wait.|||Any updates on this thread? I am looking to do the same thing (sp1 on 2003
Enterprise Server running mssql2000 sp3) in the near future.
Thanks.
"Drinian" wrote:
> We did just this on Saturday and it has been a nightmare. Everything was
> running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
> wreaked havoc!
> Our overall performance has dropped dramatically. What used to take 2
> seconds to run now takes upwards of 6. We've been working with Microsoft and
> they have absolutely no idea what the problem is and haven't really offered
> much in terms of troubleshooting ideas either.
> One suggestion we've heard is to update statictics on all tables (which I am
> doing right now) but it doesn't seem to make a difference.
> Of course Microsoft says that all of this should work fine and that W2K3 SP1
> and SQL 2000 SP3 should co-exist fine in a cluster...
> Good luck!
> "JGTKD" wrote:
> > Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
> > Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
> > issues that we want to wait.