Re: Applying SP on SQL Cluster (active/passive) after new nodes Ad

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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:98107803-0953-4B12-986E-FB82CDCBA45B@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FA6E93F9-78FC-497E-A4F0-E4D459F85CA9@xxxxxxxxxxxxxxxx
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.




.

Relevant Pages

  • Re: Problem with Outlook/ IE6? stalling
    ... One thing you could try is doing a repair on Office and install Service Pack ... Microsoft Office and Microsoft Office related News ... Also Outlook FAQ, How To's, Downloads and more... ... It's just the 3 Apps ...
    (microsoft.public.outlook)
  • Re: Problem with Outlook/ IE6? stalling
    ... One thing you could try is doing a repair on Office and install Service Pack ... Microsoft Office and Microsoft Office related News ... Also Outlook FAQ, How To's, Downloads and more... ... It's just the 3 Apps ...
    (microsoft.public.windows.inetexplorer.ie6.setup)
  • Re: MSCOMM error...or not!!??
    ... One thing that is new with the latest service pack is a change to the comm ... I've also noticed problems with some of my apps that used to work ... empty before closing the port. ... Since you have no control over the other app, ...
    (microsoft.public.vb.general.discussion)
  • Re: Do I need Office XP service pk 3 when I only have Works Suite2003
    ... Office apps use the core/common files from MS Office XP. ... isn't a separate service pack for the individual apps ... although there are minor updates specific to the apps from time ... time I installed the OfficeXP Service Pack 3 it messed up my Word 2002. ...
    (microsoft.public.word.docmanagement)
  • Re: Applying SP on SQL Cluster (active/passive) after new nodes Ad
    ... There is single-user mode for a database, and then there is single-user mode for the entire database service. ... engine up and down several times while it is applying the service pack. ... If the apps are connecting as SA, change the password before applying the SP ...
    (microsoft.public.sqlserver.clustering)
Loading