BUG: Reformat w/ TEXT Col Can Cause Errors 7114, 813, 814, 806

Last reviewed: May 2, 1997
Article ID: Q148675

The information in this article applies to:

Microsoft SQL Server, version 6.0

BUG# NT: 12208 (6.00)

SYMPTOMS

If tables involved in join statement do not have proper indexes on them, the optimizer decided to use the reformat strategy, and the select column includes TEXT field, it can cause the following errors:

 #7114 'Page %ld is not a valid text page'
 #813  'Logical page 0x%lx in database %d is already hashed'
 #814  'Keep count of buffer 0x%lx holding logical page %ld in database
        %.*s has become negative.'
 #806  'Could not find virtual page for logical page %ld in database
       '%.*s'' in tempdb and master database

WORKAROUND

Create an index base on the joined column to avoid reformatting if you have to query on TEXT field.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: sql6 tsql
Keywords : kbbug6.00 kbprg kbusage SSrvProg
Version : 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 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.