FIX: SELECT * Misleading if char or varchar Field is NULL

Last reviewed: May 1, 1997
Article ID: Q135860

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 11248 (6.00)

SYMPTOMS

If a char or varchar field in a row has a NULL character (ASCII value zero), then a SELECT * on this table shows the fields after this field as blank. A SELECT on the remaining columns works fine.

WORKAROUND

If you know which field has the NULL character, place it last in the SELECT list. For example, in the above scenario, replace the SELECT * with the following:

   SELECT y, z, x
   FROM testnull

STATUS

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

MORE INFORMATION

To replicate this problem:

   use pubs
   go
   create table testnull (x char(20) null, y char(20) null, z int)
   go
   insert into testnull values('problem_field'+char(0), 'microsoft', 20)
   go
   print ' '
   print 'RESULT OF SELECT * :'
   print ' '
   select * from testnull
   go
   print ' '
   print 'RESULT OF SELECT ON REMAINING COLUMNS:'
   print ' '
   select y, z from testnull
   go


Additional query words: sql6 tsql
Keywords : kbbug6.00 kbfix6.00.sp3 kbprg SSrvProg SSRvTran_SQL
Version : 6.0
Platform : WINDOWS


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.