DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 955693 - Last Review: December 16, 2010 - Revision: 3.0

Hotfix Download Available
View and request hotfix downloads
 
Bug #: 50002989 (SQL Hotfix)

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.

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. You create a log shipping configuration in Microsoft SQL Server 2005. After a log backup is restored on the secondary server instance, you script the log shipping configuration. Later, you use the script to re-create the log shipping configuration. After you re-create the log shipping configuration, you view the log shipping report on the monitor server. In this scenario, you can obtain only the file information about the transaction log that was last backed up on the primary database or the last transaction log that was copied and restored on the secondary server. But you cannot obtain the file information about both transaction logs. The file information about the transaction log that was last copied and restored or last backed up is missing.

CAUSE

This problem occurs because some log shipping jobs are not scripted when you script the log shipping configuration.

RESOLUTION

Please be aware that the Logshipping operations are not affected by this bug. This bug only affects the monitoring and scripting capabilities. As the "Cause" section mentions, the incorrect information in the monitor occurs because the script that was generated from the original setup is incorrect. The fix only makes sure that future attempts to generate scripts that are based on the current Logshipping configuration results in scripts that help you correctly reinstall Logshipping. However, you must also follow the additional steps that are mentioned in the "More Information" section.

To make sure that correct scripting and monitoring capabilities for your Logshipping occur, you must follow these steps:
  1. Apply this hotfix.
  2. Generate the script by using SQL Server Management Studio (SSMS).
  3. Update the script by using one of the options in the "More Information" section.
  4. Reconfigure LogShipping by using the modified script.

Cumulative update information

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
953752  (http://support.microsoft.com/kb/953752/LN/ ) Cumulative update package 9 for SQL Server 2005 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937137  (http://support.microsoft.com/kb/937137/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

After you apply the hotfix that is mentioned in this article, if you want to generate a script of your LogShipping configuration, you must use one of the following options to make sure that you obtain the correct script.

Option 1

You can use this option if your existing configuration has the monitor server either on the Primary server or on the Secondary server. Consider these scenarios:
Scenario 1: The monitor is on the Primary server. In this case, use SQL Server Management Studio (SSMS) on the Secondary server to generate and execute the script when you reconfigure LogShipping.

Scenario 2: The monitor is on the Secondary server. In this case, use SQL Server Management Studio on the Primary server to generate and execute the script when you reconfigure LogShipping.


Option 2

You can use this option for any configuration. When you use this option, you must generate the script on both the Primary and Secondary servers. And, you must manually edit each script to maintain the respective server’s information before you execute the scripts on the respective servers when reconfiguring LogShipping. To do this, follow these steps:
  1. Generate the Primary server’s LogShipping configuration script from an SSMS on the Primary Server. Then, manually edit the script to remove Secondary server’s configuration information.
  2. Generate Secondary server’s LogShipping configuration script from an SSMS on the Secondary Server. Then, manually edit the script to remove Primary server’s information.
  3. Remove your current LogShipping Configuration.
  4. Reconfigure LogShipping by doing one of the following:
    1. Execute the script from step 1 by using SQL Server Management Studio (SSMS) from the Primary server.
    2. Execute the script from step 2 by using SSMS from the Secondary server.

Option 3

Follow these steps:
  1. Use SSMS on either the Primary server or the Secondary server to generate the script.
  2. Manually edit the script to remove @ignoreremotemonitor = 1 from the primary and secondary server sections.
  3. Remove LogShipping.
  4. Reconfigure LogShipping. To do this, use SSMS on either the Primary or the Secondary servers to execute the modified script from step 2.


For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
953752  (http://support.microsoft.com/kb/953752/LN/ ) Cumulative update package 9 for SQL Server 2005 Service Pack 2

REFERENCES

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137  (http://support.microsoft.com/kb/937137/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897  (http://support.microsoft.com/kb/935897/LN/ ) An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
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  (http://support.microsoft.com/kb/913089/LN/ ) How to obtain the latest service pack for SQL Server 2005
For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=71711 (http://go.microsoft.com/fwlink/?LinkId=71711)
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  (http://support.microsoft.com/kb/822499/LN/ ) 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  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates



APPLIES TO
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
Keywords: 
kbautohotfix kbfix kbqfe kbexpertiseadvanced kbhotfixserver KB955693
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support