FIX: Multiple ORDER BY DESC May Cause 614 Errors

Last reviewed: May 1, 1997
Article ID: Q137432

The information in this article applies to:

Microsoft SQL Server, version 6.0

BUG# NT: 11164 (6.00)

SYMPTOMS

A query with multiple ORDER BY <col> DESC clauses may get a 614 error:

   A row on page X was accessed that has an illegal length of Y in database
   Z.

STATUS

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

MORE INFORMATION

If the table has had data in it but is currently empty, it is possible for a query against that table with multiple ORDER BY <col> DESC clauses to get 614 errors. The ORDER BY columns should also be such that it is a "covered" query; that is, there is an index that can be used for the ORDER BY columns.

Additional query words: sql6 614 windows nt sort
Keywords : kbbug6.00 kbfix6.00.sp2 kbprg SSrvTran_SQL
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 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.