BUG: Adding constraints through SEM sometimes unbind default o

 Last reviewed: April 8, 1997
Article ID: Q153112
The information in this article applies to:
  • Microsoft SQL Server, version 6.5

SYMPTOMS

If you create a table in which at least one of the columns uses user- defined datatype, and the user-defined datatype is bound to a default, the first time you use SQL Enterprise Manager (SEM) to add constraint to this table the default unbinds. SQL Trace shows sp_unbindefault is being called right before 'Alter table .. add constraint'. If you bind the default again explicitly, subsequent attempts to add constraints through SEM will not unbind the default again.

WORKAROUND

Use T-SQL script instead of SEM to add constraint.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words:
Keywords : kbbug6.50
Version : 6.5
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: April 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.