The information in this article applies to:
BUG #: 18930 (SQLBUG_65) SYMPTOMSUnder memory constrained conditions, running DBCC TEXTALLOC against a table containing large text values may cause SQL Server to stop processing queries and logon requests. SQL Server may also write indefinite bufwait messages or write an access violation stack dump to the errorlog in some cases. SQL Server may not seem to be responding and will not allow processing until the service is stopped and restarted. CAUSERead-ahead was being used for the text and not the base table. RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next SQL Server service pack
that contains this fix. http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later: NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.This is not an issue in SQL Server 7.0 or later. STATUSMicrosoft has confirmed this to be a problem in SQL Server version 6.5 Service Pack 5a. MORE INFORMATIONThe following error may be written to the errorlog, which may cause a concern for reconfiguring sp_configure settings: Increasing the read ahead settings may provide some immediate relief, but the likelihood of reoccurrence is increased as more text is added to the table. Additional query words:
Keywords : kbSQLServ650sp5bug kbbug6.50.sp5 |
Last Reviewed: January 26, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |