FIX: The replication on the server does not work any longer when you manually fail over databases in SQL Server 2005

Article translations Article translations
Article ID: 912471 - View products that this article applies to.
BUG #: 415917 (SQLBUDT)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
Expand all | Collapse all

On This Page

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by the hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

Consider the following scenario. In Microsoft SQL Server 2005, you set up database mirroring for more than one database to run in high-availability mode. You also configure the databases as publishers for transactional replication. You set up a replication to replicate data between the principal server and the mirror server. In this scenario, when you restart the principal server and manually fail over the databases, the replication on the server does not work any longer.

CAUSE

This problem occurs because the sys.databases catalog view is updated incorrectly after you fail over the database that is mirrored. The replication is disabled because the is_published column of the sys.databases catalog view is set back to 0.

RESOLUTION

Service pack information

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

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have SQL Server 2005 installed on the computer.

Restart information

You do not have to restart the computer after you apply this hotfix. However, you must restart the SQL Server service for the hotfix to take effect.

Registry information

You do not have to change the registry after you apply this hotfix.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) 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.
SQL Server 2005 32-bit versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.smo.dll9.0.1514.01,559,25605-Jan-200607:37x86
Msxmlsql.dll2005.90.1514.0899,63805-Jan-200607:13x86
Osql.exe2005.90.1514.051,41605-Jan-200607:37x86
Sqlaccess.dll2005.90.1514.0349,40005-Jan-200607:37x86
Sqlservr.exe2005.90.1514.028,778,76805-Jan-200607:38x86
SQL Server 2005 IA-64 versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.smo.dll9.0.1514.01,551,06405-Jan-200610:14x86
Osql.exe2005.90.1514.0123,09605-Jan-200610:14IA-64
Sqlaccess.dll2005.90.1514.0351,44805-Jan-200610:14x86
Sqlservr.exe2005.90.1514.072,190,16805-Jan-200610:15IA-64
SQL Server 2005 x64 versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.smo.dll9.0.1514.01,551,06406-Jan-200603:42x86
Osql.exe2005.90.1514.083,67206-Jan-200603:42x64
Sqlaccess.dll2005.90.1514.0356,56806-Jan-200603:42x86
Sqlservr.exe2005.90.1514.039,468,76006-Jan-200603:43x64
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 1.

MORE INFORMATION

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Steps to reproduce the problem

  1. Set up three instances of SQL Server 2005 on the following three computers:
    • The principal server
    • The mirror server
    • The witness server
  2. Set up database mirroring for two user databases on the servers in high-availability mode.

    For more information about high-availability mode, see the "Synchronous Database Mirroring (High-Availability and High-Protection Modes)" topic in SQL Server 2005 Books Online.
  3. Set up a replication on the two databases between the principal server and the mirror server.
  4. Restart the principal server to fail over the databases in the next step.
  5. Manually fail over the principal server to the mirror server.

    For more information about how to manually fail over the principal server, see the "Transact-SQL Settings and Database Mirroring Operating Modes" topic in SQL Server 2005 Books Online.
When you complete these steps, the replication on the server does not work any longer.

REFERENCES

For more information, see the following topics in SQL Server 2005 Books Online:
  • Database Mirroring
  • SQL Server Replication Overview
  • Transactional Replication Overview

Properties

Article ID: 912471 - Last Review: October 9, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Developer Edition
Keywords: 
kbautohotfix kbsql2005repl kbsqlserv2005fix kbsql2005presp1fix kbfix kbbug kbhotfixserver kbqfe KB912471

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com