FIX: Replication Removed from Database After Restore WITH RECOVERY (329499)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)
  • Microsoft SQL Server 7.0

This article was previously published under Q329499
BUG #: 362401 (SHILOH_BUGS)

BUG #: 102929 (SQLBUG_70)

SYMPTOMS

When you restore a published database to the same server and database name, SQL Server may not preserve the replication settings for that database.

RESOLUTION

SQL Server 2000
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack


NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft SQL Server 2000 or Microsoft SQL Server 7.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Microsoft SQL Server 2000

   Date       Time       Version         Size              File name
   --------------------------------------------------------------------

   09/25/02   18:17:47   2000.80.689.0   7,467,089 bytes   Sqlservr.exe
				
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

Microsoft SQL Server 7.0

   Date       Time       Version     Size              File name
   --------------------------------------------------------------------

   09/26/02   16:27:50   7.00.1079   5,058,832 bytes   Sqlservr.exe
				
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
SQL Server 2000
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

MORE INFORMATION

The "Restoring Backups of Replicated Databases to the Same Server and Database" topic in SQL Server Books Online states that replication is typically preserved:

In most cases, restoring a backup to the same server and database from which it was created will preserve your replication settings.


Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbSQLServ2000preSP3fix kbSQLServ2000sp3fix KB329499