Solved

How does the SQL Server 2000 upgrade from SP1 to SP4 affect the log shipping process?

Posted on 2008-06-26
3
284 Views
Last Modified: 2008-09-14
We are currently running the Log Shipping Process to keep our Backup server (SQL Server 2000 SP1) in synch with the Primary server (SQL Server 2000 SP1).
I am planning to upgrade the both the Primary and the Backup server from SP1 to SP4 for which I will
stop the LogShipping jobs on the primary and the backup server, install the SP4 update on both the servers and start the jobs back again after the upgrade.
Is there something different that has to be done after the upgrade to make sure that the log shipping process is not affected in any way?
0
Comment
Question by:mitsdev
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 10

Accepted Solution

by:
TOPIO earned 500 total points
ID: 21878756
The exact procedure is here:
http://download.microsoft.com/download/1/B/D/1BDF5B78-584E-4DE0-B36F-C44E06B0D2A3/ReadmeSql2k32sp4.htm#_1462462_considerations_for_an_instance_i_gq59

Log Shipping and Database Components
Because non-writable databases do not cause Setup to fail, you need not remove log shipping before upgrading to Database Components SP4. However, if the database is shipping logs to a database that is a replication publisher, you must do the following:

Take the database offline before you apply SP4.


Apply SP4 to the instance.


Bring the database back online.


Log on to Query Analyzer and run the following script:
USE master
GO
EXEC sp_vpupgrade_replication
GO
If you apply SP4 without having taken offline all non-writable databases that ship logs to publication databases, you receive this error:

Error Running Script sp_vpupgrade_replication (1)

If you receive this error, follow the preceding procedure.

Note   During installation, Setup makes no distinction between read-only databases and databases that are offline or in a suspect state. If a replication database or filegroup is offline or in a suspect state during setup and is involved in a replication topology, you must reapply the service pack after making the database writable



0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Let's review the features of new SQL Server 2012 (Denali CTP3). It listed as below: PERCENT_RANK(): PERCENT_RANK() function will returns the percentage value of rank of the values among its group. PERCENT_RANK() function value always in be…
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Via a live example, show how to setup several different housekeeping processes for a SQL Server.

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question