FIX: No Errors When Trying to Find Null Values in NOT NULL Col

 Last reviewed: May 2, 1997
Article ID: Q142760

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

SYMPTOMS

If you try to find null values in columns defined as NOT NULL, then according to documentation SQL Server should generate an error message. Error messages are displayed in SQL Server 4.21a but not SQL Server 6.0.

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

The "Transact-SQL Reference" and "Books Online" mention that if you try to find null values in columns defined as NOT NULL, SQL Server generates an error message. This is a documentation error in version 6.0. The behavior was changed in 6.0 by design. The following script will illustrate the error:

create table t (x int not null) go insert into t values (1) go select * from t where x is null

Additional query words: SQL6 docs
Keywords : kbbug6.00 kbfix6.00.sp3 SSrvDoc_Err
Version : 6.0
Platform : WINDOWS
Issue type : kbdocerr

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.