FIX: Error message when you perform a piecemeal restore operation after you enable vardecimal database compression in SQL Server 2005 Service Pack 2: "Piecemeal restore is not supported when an upgrade is involved"

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

Consider the following scenario. You enable vardecimal database compression for a database in Microsoft SQL Server 2005 Service Pack 2 (SP2). You perform a piecemeal restore operation on the database. In this scenario, you receive error messages that resemble the following:After the operation fails, the file group may be marked as defunct.

This problem occurs because the database version is changed from 611 to 612 when you enable vardecimal database compression for a database. The piecemeal restore logic has an incorrect test for the current version number. Therefore, the piecemeal restore operation fails.

Cumulative update information

To resolve this problem, obtain the cumulative update package (build 3161) for SQL Server 2005 SP2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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: 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 SP2 installed on the computer. 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:

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not 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 of 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 Database Engine, 32-bit version

SQL Server 2005 Database Engine, x64-based version

SQL Server 2005 Database Engine, Itanium architecture version

To work around this problem, restore the whole database instead of using a piecemeal restore operation.

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

After you apply this hotfix, this problem will not occur in any later piecemeal restore operations. If this problem does occur, the database has a file group that is in the defunct state. You must recover the database by performing a complete database restore of the database. After you apply this hotfix, the complete database restore can be done in a piecemeal manner. The database restore will restore one file group at a time. However, you cannot restore only the defunct file group. 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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: