Select the product you need help with
FIX: The value of the automatic growth increment of a database file may be very large in SQL Server 2005Article ID: 917887 - View products that this article applies to. 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 PageSUMMARYThis article describes the following about this hotfix release:
SYMPTOMSWhen 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.
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
(http://support.microsoft.com/kb/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 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: http://support.microsoft.com/contactus/?ws=support 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesYou must have SQL Server 2005 to apply this hotfix.Restart informationYou 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 informationYou do not have to change the registry.Hotfix file informationThis 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 versionCollapse this table
SQL Server 2005 x64-based versionCollapse this table
SQL Server 2005 Itanium architecture versionCollapse this table
WORKAROUNDTo 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.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONIf 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
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
PropertiesArticle ID: 917887 - Last Review: October 9, 2011 - Revision: 2.0 APPLIES TO
|
Back to the top
