Article ID: 919611
Article Last Modified on 11/4/2007
APPLIES TO
- Microsoft SQL Server 2005 Service Pack 1
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 with Service Pack 1 (SP1), 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 the original version of SQL Server 2005. A different hotfix corrects this problem on the original version of SQL Server 2005.
For more information about the hotfix for the original version of SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:
917887 FIX: The value of the automatic growth increment of a database file may be very large in SQL Server 2005
RESOLUTION
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
You must have SQL Server 2005 with SP1 to apply this hotfix.
For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005
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 name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.sqlserver.sqlenum.dll | 9.0.2156.0 | 908,064 | 23-May-2006 | 10:04 | x86 |
| Ms.ss.mgdsqldumper.dll | 2005.90.2156.0 | 75,552 | 23-May-2006 | 10:04 | x86 |
| Sbmsmdlocal.dll | 9.0.2156.0 | 15,661,344 | 23-May-2006 | 10:05 | x86 |
| Sqlaccess.dll | 2005.90.2156.0 | 347,936 | 23-May-2006 | 10:04 | x86 |
| Sqlservr.exe | 2005.90.2156.0 | 28,937,560 | 23-May-2006 | 10:05 | x86 |
SQL Server 2005 x64-based version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.sqlserver.sqlenum.dll | 9.0.2156.0 | 875,296 | 24-May-2006 | 11:08 | x86 |
| Ms.ss.mgdsqldumper.dll | 2005.90.2156.0 | 91,424 | 23-May-2006 | 10:04 | x64 |
| Sbmsmdlocal.dll | 9.0.2156.0 | 15,661,344 | 23-May-2006 | 10:05 | x86 |
| Sqlaccess.dll | 2005.90.2156.0 | 355,104 | 24-May-2006 | 11:09 | x86 |
| Sqlservr.exe | 2005.90.2156.0 | 39,345,952 | 24-May-2006 | 11:08 | x64 |
SQL Server 2005 Itanium architecture version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.sqlserver.sqlenum.dll | 9.0.2156.0 | 875,296 | 24-May-2006 | 02:50 | x86 |
| Ms.ss.mgdsqldumper.dll | 2005.90.2156.0 | 163,104 | 23-May-2006 | 10:04 | IA-64 |
| Sbmsmdlocal.dll | 9.0.2156.0 | 48,731,936 | 24-May-2006 | 02:49 | IA-64 |
| Sqlaccess.dll | 2005.90.2156.0 | 349,472 | 24-May-2006 | 02:50 | x86 |
| Sqlservr.exe | 2005.90.2156.0 | 72,186,144 | 24-May-2006 | 02:49 | IA-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
Keywords: kbhotfixserver kbfix kbexpertiseadvanced kbqfe kbpubtypekc KB919611
