FIX: The value of the automatic growth increment of a database file may be very large in SQL Server 2005 (917887)


The information in this article applies to:

  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Workgroup
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
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.

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by this 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

When you examine the value for the automatic growth increment of a database file in the original version of SQL Server 2005, you may see a very large number. For example, the value for the automatic growth increment of a database file may be 12800%.

This problem occurs when you perform all the following operations before you examine the value.
  • You create the database by setting a percentage value for the automatic growth increment of the database file.
  • You manually change the value for the automatic growth increment of the database file to be a fixed size value.
  • You perform one of the following operations.
    • You restart the SQL Server service.
    • You take the database offline, and then bring the database online.
    • You detach the database, and then attach the database.
Note The database files include the .mdf primary data file, the .ndf secondary data files, and the .ldf transaction log files.

This problem also exists in SQL Server 2005 with Service Pack 1 (SP1). A different hotfix corrects this problem for SQL Server 2005 with SP1.

For more information about the hotfix for the problem on SQL Server 2005 with SP1, click the following article number to view the article in the Microsoft Knowledge Base:

919611 FIX: The value of the automatic growth increment of a database file may be very large in SQL Server 2005 with Service Pack 1

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2005 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have SQL Server 2005 to apply this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix. However, if you have already been affected by this problem, you must apply the hotfix, and then you must perform the method that is described in the "Workaround" section to revert the database files to a healthy state.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only the files that are required to correct the problem that this article describes. 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 32-bit version

File nameFile versionFile sizeDateTimePlatform
Logread.exe2005.90.1550.0397,08813-Jun-200608:46x86
Microsoft.sqlserver.replication.dll2005.90.1550.01,608,48013-Jun-200608:46x86
Microsoft.sqlserver.smo.dll9.0.1550.01,559,32813-Jun-200608:46x86
Microsoft.sqlserver.sqlenum.dll9.0.1550.0895,77613-Jun-200608:46x86
Msmdredir.dll9.0.1550.03,929,88813-Jun-200608:47x86
Osql.exe2005.90.1550.051,48813-Jun-200608:45x86
Replrec.dll2005.90.1550.0781,08813-Jun-200608:46x86
Sbmsmdlocal.dll9.0.1550.015,626,52813-Jun-200608:48x86
Sqlaccess.dll2005.90.1550.0349,47213-Jun-200608:46x86
Sqldiag.exe2005.90.1550.0960,28813-Jun-200608:46x86
Sqlservr.exe2005.90.1550.028,789,08013-Jun-200608:48x86

SQL Server 2005 x64-based version

File nameFile versionFile sizeDateTimePlatform
Logread.exe2005.90.1550.0521,50413-Jun-200616:29x64
Microsoft.sqlserver.replication.dll2005.90.1550.01,813,79213-Jun-200616:30x64
Microsoft.sqlserver.smo.dll9.0.1550.01,551,13613-Jun-200616:30x86
Microsoft.sqlserver.sqlenum.dll9.0.1550.0863,00813-Jun-200616:30x86
Msmdlocal.dll9.0.1550.015,626,52813-Jun-200608:48x86
Msmdredir.dll9.0.1550.03,929,88813-Jun-200608:47x86
Osql.exe2005.90.1550.083,74413-Jun-200616:28x64
Replrec.dll2005.90.1550.01,007,39213-Jun-200616:30x64
Sqlaccess.dll2005.90.1550.0356,64013-Jun-200616:29x86
Sqldiag.exe2005.90.1550.01,127,71213-Jun-200616:30x64
Sqlservr.exe2005.90.1550.039,415,07213-Jun-200616:27x64

SQL Server 2005 Itanium architecture version

File nameFile versionFile sizeDateTimePlatform
Logread.exe2005.90.1550.01,091,36013-Jun-200614:02IA-64
Microsoft.sqlserver.replication.dll2005.90.1550.02,521,88813-Jun-200614:02IA-64
Microsoft.sqlserver.smo.dll9.0.1550.01,551,13613-Jun-200614:02x86
Microsoft.sqlserver.sqlenum.dll9.0.1550.0863,00813-Jun-200614:02x86
Msmdredir.dll9.0.1550.06,079,26413-Jun-200614:03IA-64
Osql.exe2005.90.1550.0123,16813-Jun-200614:00IA-64
Replrec.dll2005.90.1550.02,137,88813-Jun-200614:02IA-64
Sbmsmdlocal.dll9.0.1550.048,586,01613-Jun-200614:00IA-64
Sqlaccess.dll2005.90.1550.0351,52013-Jun-200614:01x86
Sqldiag.exe2005.90.1550.01,637,15213-Jun-200614:02IA-64
Sqlservr.exe2005.90.1550.072,232,22413-Jun-200614:00IA-64

WORKAROUND

To work around this problem, change the automatic growth increment of the database file back to a percentage value. We recommend that you do not set the automatic growth increment to be a fixed value if the automatic growth increment of a database file is a percentage value.

Additionally, you can temporarily work around this issue by resetting the value for the automatic growth increment of the file to the fixed value that you previously specified. However, the problem will not be resolved permanently unless you apply the hotfix. You will encounter this problem again if you perform one of the following operations.
  • You restart the SQL Server service.
  • You take the database offline, and then bring the database online.
  • You detach the database, and then attach the database.

STATUS

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

MORE INFORMATION

If you want to set the automatic growth increment of a database file to a different value, and the current value for the automatic growth increment of the database file is a percentage value, you can continue to use another percentage value instead of a fixed value. By doing this, you can avoid the problem that this article describes.

For more information about the naming schema for Microsoft 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

Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbsql2005engine kbHotfixServer kbExpertiseAdvanced kbQFE kbfix kbpubtypekc KB917887 kbAudITPRO kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.