FIX: Changes in the publisher database are not replicated to the subscribers in a transactional replication if the publisher database runs exposed in a database mirroring session in SQL Server 2005

Applies to: Microsoft SQL Server 2005 Service Pack 2

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 in the previous SQL Server 2005 fix release.

SUMMARY


This article describes the following information 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 configure a database to be the principal database for database mirroring.
  • You then configure the database to be the publisher database in a transactional replication.
  • In a database mirroring session, the publisher database runs exposed.
  • You make some changes to the publisher database.

In this scenario, the changes are not replicated to the subscribers.

CAUSE


This  occurs because Log Reader Agent does not copy the transactions that are marked for replication from the transaction log into the distribution database. Log Reader Agent cannot read past a specific log sequence number (LSN). This specific LSN represents the last LSN that has been hardened to the transaction log of the mirror database.

RESOLUTION


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's 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 don't 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 website:

http://support.microsoft.com/contactus/?ws=support

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you don't see your language, it is because a hotfix isn't available for that language.

Prerequisites

You must have SQL Server 2005 Service Pack 2 (SP2) installed to apply this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 2, 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

Restart information

You don't have to restart the computer after you apply this hotfix.

Registry information

You don't have to change the registry.

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 item in Control Panel.

SQL Server 2005, 32-bit version

File name

File version

File size

Date

Time

Platform

Microsoft.sqlserver.maintenanceplantasks.dll

9.0.3169.0

296,304

11-May-2007

18:58

x86

Msmdlocal.dll

9.0.3169.0

15,943,536

11-May-2007

18:58

x86

Rdistcom.dll

2005.90.3169.0

644,464

11-May-2007

18:58

x86

Sqlaccess.dll

2005.90.3169.0

350,576

11-May-2007

18:58

x86

Sqlservr.exe

2005.90.3169.0

29,187,952

11-May-2007

18:58

x86

SQL Server 2005, Itanium architecture version

File name

File version

File size

Date

Time

Platform

Microsoft.sqlserver.maintenanceplantasks.dll

9.0.3169.0

296,304

11-May-2007

17:58

x86

Msmdlocal.dll

9.0.3169.0

49,887,088

12-May-2007

03:06

IA-64

Rdistcom.dll

2005.90.3169.0

1,885,040

12-May-2007

03:06

IA-64

Sqlaccess.dll

2005.90.3169.0

352,112

12-May-2007

03:06

x86

Sqlservr.exe

2005.90.3169.0

72,609,648

12-May-2007

03:07

IA-64

STATUS


This behavior is by design.

MORE INFORMATION


After you apply the hotfix, you must globally enable trace flag 1448 on the instance of the publisher database. Then, Log Reader Agent will always copy the transactions that are marked for replication from the transaction log into the distribution database.

Note If you are running SQL Server 2008, you can also enable trace flag 1448 to resolve this issue.

To globally enable trace flag 1448 on the instance of the publisher database, follow these steps:

  1. Start SQL Server Configuration Manager.
  2. In SQL Server Configuration Manager, click SQL Server 2005 Services.
  3. In the details pane, right-click the instance, and then click Properties.
  4. In the SQL Server (InstanceName) dialog box, click the Advanced tab, and then click Startup Parameters.
  5. At the end of the original text, type -T1448.
  6. Restart the SQL Server service. 

You can obtain the last LSN that has been hardened to the mirror database by querying the mirroring_failover_lsn column of the sys.database_mirroring catalog view.

A principal database runs exposed when one of the following conditions is true:

  • You pause the database mirroring session.
  • The connection between the principal server and the mirror server is lost.

To pause a database mirroring session, you can run the ALTER DATABASE statement by using the SET PARTNER SUSPEND option.

REFERENCES


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