 | Hotfix Download Available |
FIX: You may experience very large growth increments of a principal database after you manually fail over a database mirroring session in SQL Server 2005| Article ID | : | 925277 | | Last Review | : | November 20, 2007 | | Revision | : | 1.6 |
Bug #: 50000246 (SQL Hotfix)
NoticeMicrosoft 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.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 | | • | Information about whether you must restart the computer after you install the
hotfix package | | • | Information about whether the hotfix package is replaced by any other hotfix
package | | • | Information about whether you must make any registry changes | | • | The files that are contained in the hotfix
package |
Back to the top
SYMPTOMSAfter you manually fail over a database mirroring session in SQL Server 2005, the growth type of the principal database may change to percentage instead of fixed size. Therefore, you experience very large growth increments of the transaction log files and data files of the principal database. This problem occurs if the following conditions are true: | • | The ALTER DATABASE statement is used on the principal database to change
the file growth to a fixed file size growth. | | • | Before the failover occurs, the growth option in the sysfiles
table of the principal database does not match the growth option in the
master.dbo.sysaltfiles system table on the new principal server. |
The most common scenario is that this problem only affects the growth
of the transaction log files of the database. However, this problem can also affect data
files in some scenarios. Back to the top
RESOLUTIONA 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, 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 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. To create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" section and the online request forms display 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. PrerequisitesYou must have SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix. For more information, click the following
article number to view the article in the Microsoft Knowledge Base: 913089 (http://support.microsoft.com/kb/913089/)
How to obtain the latest service pack for SQL Server 2005
Restart informationYou do not have to restart the computer after you apply this
hotfix. Registry informationYou do not have to change the registry. Hotfix file informationThis 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 32-bit version| File name | File version | File
size | Date | Time | Platform |
|---|
| Logread.exe | 2005.90.2198.0 | 398,112 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.analysisservices.adomdclient.dll | 9.0.2198.0 | 543,520 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.analysisservices.deploymentengine.dll | 9.0.2198.0 | 138,016 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.analysisservices.dll | 9.0.2198.0 | 1,215,264 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2198.0 | 75,552 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.sqlserver.sqlenum.dll | 9.0.2198.0 | 908,064 | 12-Oct-2006 | 23:32 | x86 | | Msasxpress.dll | 9.0.2198.0 | 22,304 | 12-Oct-2006 | 23:32 | x86 | | Msgprox.dll | 2005.90.2198.0 | 197,920 | 12-Oct-2006 | 23:32 | x86 | | Msmdlocal.dll | 9.0.2198.0 | 15,608,096 | 12-Oct-2006 | 23:32 | x86 | | Msmdredir.dll | 9.0.2198.0 | 3,990,304 | 12-Oct-2006 | 23:32 | x86 | | Mssqlsystemresource.ldf | Not
applicable | 524,288 | 12-Oct-2006 | 20:50 | Not
applicable | | Mssqlsystemresource.mdf | Not
applicable | 40,108,032 | 12-Oct-2006 | 20:50 | Not
applicable | | Replprov.dll | 2005.90.2198.0 | 547,616 | 12-Oct-2006 | 23:32 | x86 | | Replrec.dll | 2005.90.2198.0 | 782,112 | 12-Oct-2006 | 23:32 | x86 | | Sqlaccess.dll | 2005.90.2198.0 | 347,936 | 12-Oct-2006 | 23:33 | x86 | | Sqlagent90.exe | 2005.90.2198.0 | 318,752 | 12-Oct-2006 | 23:33 | x86 | | Sqlservr.exe | 2005.90.2198.0 | 28,963,160 | 12-Oct-2006 | 23:33 | x86 | | Sysdbupg.sql | Not
applicable | 192,346 | 21-Aug-2006 | 15:01 | Not
applicable | | Xpstar90.dll | 2005.90.2198.0 | 292,640 | 12-Oct-2006 | 23:33 | x86 | | Xpstar90.rll | 2005.90.2198.0 | 152,864 | 12-Oct-2006 | 23:32 | x86 |
SQL Server 2005 x64-based version| File name | File version | File
size | Date | Time | Platform |
|---|
| Logread.exe | 2005.90.2198.0 | 522,528 | 15-Oct-2006 | 13:16 | x64 | | Microsoft.analysisservices.adomdclient.dll | 9.0.2198.0 | 543,520 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.analysisservices.adomdclient.dll | 9.0.2198.0 | 543,520 | 15-Oct-2006 | 13:16 | x86 | | Microsoft.analysisservices.deploymentengine.dll | 9.0.2198.0 | 138,016 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.analysisservices.dll | 9.0.2198.0 | 1,215,264 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2198.0 | 75,552 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2198.0 | 91,424 | 15-Oct-2006 | 13:16 | x64 | | Microsoft.sqlserver.sqlenum.dll | 9.0.2198.0 | 875,296 | 15-Oct-2006 | 13:16 | x86 | | Msasxpress.dll | 9.0.2198.0 | 22,304 | 12-Oct-2006 | 23:32 | x86 | | Msasxpress.dll | 9.0.2198.0 | 27,424 | 15-Oct-2006 | 13:16 | x64 | | Msgprox.dll | 2005.90.2198.0 | 259,360 | 15-Oct-2006 | 13:16 | x64 | | Msmdlocal.dll | 9.0.2198.0 | 15,608,096 | 12-Oct-2006 | 23:32 | x86 | | Msmdredir.dll | 9.0.2198.0 | 3,990,304 | 12-Oct-2006 | 23:32 | x86 | | Mssqlsystemresource.ldf | Not
applicable | 524,288 | 12-Oct-2006 | 20:50 | Not
applicable | | Mssqlsystemresource.mdf | Not
applicable | 40,108,032 | 12-Oct-2006 | 20:50 | Not
applicable | | Replprov.dll | 2005.90.2198.0 | 745,248 | 15-Oct-2006 | 13:16 | x64 | | Replrec.dll | 2005.90.2198.0 | 1,008,416 | 15-Oct-2006 | 13:16 | x64 | | Sqlaccess.dll | 2005.90.2198.0 | 355,104 | 15-Oct-2006 | 13:16 | x86 | | Sqlagent90.exe | 2005.90.2198.0 | 389,920 | 15-Oct-2006 | 13:16 | x64 | | Sqlservr.exe | 2005.90.2198.0 | 39,344,928 | 15-Oct-2006 | 13:17 | x64 | | Sysdbupg.sql | Not
applicable | 192,346 | 21-Aug-2006 | 15:01 | Not
applicable | | Xpstar90.dll | 2005.90.2198.0 | 540,960 | 15-Oct-2006 | 13:17 | x64 | | Xpstar90.rll | 2005.90.2198.0 | 153,376 | 15-Oct-2006 | 13:16 | x64 |
SQL Server 2005 Itanium architecture version| File name | File version | File
size | Date | Time | Platform |
|---|
| Logread.exe | 2005.90.2198.0 | 1,095,456 | 13-Oct-2006 | 09:06 | IA-64 | | Microsoft.analysisservices.adomdclient.dll | 9.0.2198.0 | 543,520 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.analysisservices.adomdclient.dll | 9.0.2198.0 | 543,520 | 13-Oct-2006 | 09:06 | x86 | | Microsoft.analysisservices.deploymentengine.dll | 9.0.2198.0 | 138,016 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.analysisservices.dll | 9.0.2198.0 | 1,215,264 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2198.0 | 75,552 | 12-Oct-2006 | 23:32 | x86 | | Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2198.0 | 163,104 | 13-Oct-2006 | 09:06 | IA-64 | | Microsoft.sqlserver.sqlenum.dll | 9.0.2198.0 | 875,296 | 13-Oct-2006 | 09:06 | x86 | | Msasxpress.dll | 9.0.2198.0 | 22,304 | 12-Oct-2006 | 23:32 | x86 | | Msasxpress.dll | 9.0.2198.0 | 55,072 | 13-Oct-2006 | 09:06 | IA-64 | | Msgprox.dll | 2005.90.2198.0 | 542,496 | 13-Oct-2006 | 09:07 | IA-64 | | Msmdlocal.dll | 9.0.2198.0 | 48,590,112 | 13-Oct-2006 | 09:07 | IA-64 | | Msmdredir.dll | 9.0.2198.0 | 6,244,640 | 13-Oct-2006 | 09:07 | IA-64 | | Mssqlsystemresource.ldf | Not
applicable | 524,288 | 12-Oct-2006 | 20:50 | Not
applicable | | Mssqlsystemresource.mdf | Not
applicable | 40,108,032 | 12-Oct-2006 | 20:50 | Not
applicable | | Replprov.dll | 2005.90.2198.0 | 1,617,184 | 13-Oct-2006 | 09:07 | IA-64 | | Replrec.dll | 2005.90.2198.0 | 2,141,472 | 13-Oct-2006 | 09:07 | IA-64 | | Sqlaccess.dll | 2005.90.2198.0 | 349,472 | 13-Oct-2006 | 09:07 | x86 | | Sqlagent90.exe | 2005.90.2198.0 | 1,141,024 | 13-Oct-2006 | 09:07 | IA-64 | | Sqlservr.exe | 2005.90.2198.0 | 72,226,592 | 13-Oct-2006 | 09:07 | IA-64 | | Sysdbupg.sql | Not
applicable | 192,346 | 21-Aug-2006 | 15:01 | Not
applicable | | Xpstar90.dll | 2005.90.2198.0 | 951,072 | 13-Oct-2006 | 09:01 | IA-64 | | Xpstar90.rll | 2005.90.2198.0 | 152,352 | 13-Oct-2006 | 09:07 | IA-64 |
Back to the top
WORKAROUNDTo work around this issue, follow these steps:
| 1. | Use the ALTER DATABASE statement to set the file growth to a
percentage growth. | | 2. | Perform a manual failover of the database mirroring
session. | | 3. | Use the ALTER DATABASE statement to set the file growth to the
correct type and amount. |
Back to the top
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. Back to the top
REFERENCES
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 (http://support.microsoft.com/kb/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 (http://support.microsoft.com/kb/824684/)
Description of the standard
terminology that is used to describe Microsoft software updates
For more information about a similar issue, 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
Back to the top
APPLIES TO| • | Microsoft SQL Server 2005 Standard Edition | | • | Microsoft SQL Server 2005 Developer Edition | | • | Microsoft SQL Server 2005 Enterprise Edition | | • | Microsoft SQL Server 2005 Standard X64 Edition | | • | Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems | | • | Microsoft SQL Server 2005 Enterprise X64 Edition | | • | Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems |
Back to the top
| kbautohotfix kbexpertiseadvanced kbtshoot kbsql2005engine kbfix kbhotfixserver kbqfe kbpubtypekc KB925277 |
Back to the top
| Other Support Options - Contact Microsoft
Phone Numbers, Support Options and Pricing, Online Help, and more. - Customer Service
For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more. - Newsgroups
Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.
|
|