BUG: DocErr: IS NULL Now Supports TEXT and IMAGE Columns

Last reviewed: April 30, 1997
Article ID: Q132277
The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 10212 (6.0)

SYMPTOMS

The Microsoft SQL Server "Database Developer's Companion" incorrectly states on page 72 that the only WHERE conditions you can use on TEXT columns are LIKE and NOT LIKE. These conditions cannot determine the NULL status of a TEXT or IMAGE column. Microsoft SQL Server version 6.0 adds functionality to support using IS NULL and IS NOT NULL with TEXT and IMAGE columns.

WORKAROUND

In previous versions of SQL Server, it was illegal to use IS NULL and IS NOT NULL with TEXT and IMAGE columns, and doing so would result in error message 403, indicating an invalid operation. SQL Server 6.0 has been enhanced to allow IS NULL and IS NOT NULL to work correctly with TEXT and IMAGE columns.

The following query gives an example of the new behavior:

   use pubs
   go
   drop table junk
   go
   create table junk (a text null, b image null)
   go
   insert into junk (a) values ('a is not null but b is')
   insert into junk (b) values ('b is not null but a is')
   go
   select * from junk where a is null
   go
   select * from junk where b is not null
   go
   select * from junk where a like null
   go

STATUS

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


Additional query words: sql6 Windows NT
Keywords : kbbug6.00 kbother SSrvDoc_Err SSrvWinNT
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: April 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.