FIX: Error message when you upgrade a database from SQL Server 2000 Windows CE Edition 2.0 to SQL Server 2005 Mobile Edition: "The database file is larger than the configured maximum database size"

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

When you run the Upgrade.exe file to upgrade a database from Microsoft SQL Server 2000 Microsoft Windows CE Edition 2.0 (SQL Server CE) to Microsoft SQL Server 2005 Mobile Edition, you receive the following error message:This problem occurs if the database is larger than 128 megabytes (MB).

Note You receive a similar error message when you upgrade a database from SQL Server CE to Microsoft SQL Server 2005 Compact Edition.

This problem occurs because the Upgrade.exe file makes a connection to the source database when you run the Upgrade.exe file. Additionally, the Upgrade.exe file specifies a default database size of 128 MB. The Upgrade.exe file does not override this default database size if the database is larger than 128 MB.

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.

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, submit a request to 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

No prerequisites are required to apply this hotfix.

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 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.

Microsoft Windows CE 5.0 ARMV4i-based device

Microsoft Windows Mobile 5.0 ARMV4i-based device

Microsoft Windows Powered Pocket PC 2003 ARMV4-based device

To work around this problem, reduce the size of the database to be smaller than 128 MB before you upgrade the database.

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

For more information about other hotfixes that are contained in the same hotfix package, click the following article numbers to view the articles in the Microsoft Knowledge Base: 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: