FIX: Updating a Record w/ NULL Text Field Can Cause 2574 Error

Last reviewed: May 1, 1997
Article ID: Q136864

The information in this article applies to:

Microsoft SQL Server, versions 4.21a and 6.0

BUG# NT: 9691 (4.21a)

SYMPTOMS

If you insert a NULL into a text field and then update the record that the text field belongs to and leave the text field NULL, a DBCC TEXTALLOC will show error 2574:

   Index page number %ld is empty. Status = 0x%x.

CAUSE

If the empty text page is the first page in the text chain, DBCC TEXTALLOC will erroneously report a 2574 error.

WORKAROUND

The error message is an erroneous error message and therefore is no cause for concern. To clear the message, you can move the date using bcp, transfer manager, or a SELECT INTO. You can also update the record and include valid, not null data for the text field.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.00. This problem was corrected in Service Pack 1 for SQL Server version 6.0. For more information, contact your primary support provider.

Additional query words: sql6 textalloc 2574
Keywords : kbbug4.21a kbbug6.00 kbfix6.00.sp1 kbprg SSrvProg
Version : 4.21a 6.0
Platform : WINDOWS
Issue type : kberrmsg

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.