Microsoft KB Archive/157980

= BUG: Example of Sp_addtype Is Unclear in the Documentation =

Article ID: 157980

Article Last Modified on 3/14/2005

-

APPLIES TO


 * Microsoft SQL Server 6.0 Standard Edition
 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q157980



BUG #: 16126 (Windows: 6.50.201)



SYMPTOMS
Example B in the "Transact-SQL Reference" section on sp_addtype does not always add a user-defined datatype that defaults to allowing nulls.



STATUS
Microsoft has confirmed this to be a problem in the products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.



MORE INFORMATION
In the section on the nulltype parameter for sp_addtype, the "Transact-SQL Reference" correctly states that if a null value is specified for this parameter, the default nullability setting of the data type will be based on the current ansinull setting for the connection. You can determine what the current setting is by using the system function getansinull; you can control the setting with the SET and sp_dboption commands.

The following command in example B is supposed to always enable the default nullability of a user-defined datatype:

  sp_addtype birthday, datetime, NULL

However, specifying NULL for the nulltype parameter passes a null value into sp_addtype, not the string "NULL." The command above will therefore set birthday's nullability default to the current ansinull setting. If ansinull is off, then birthday will default to not null. If you want a datatype to default to allowing nulls regardless of the current setting of ansinull, you should instead use the following command:

  sp_addtype birthday, datetime, 'NULL'

Additional query words: wrong incorrect erroneously erroneous

Keywords: kbbug kbusage KB157980

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.