FIX: Script Generation Using SEM Overlooks Default Bindings

Last reviewed: May 14, 1997
Article ID: Q139554

The information in this article applies to:

Microsoft SQL Server, version 6.0

BUG# NT: 11912 (6.00)

SYMPTOMS

Script generation in SQL Enterprise Manager (SEM) overlooks default bindings.

If there is a default bound to a particular column in a table in the database, the script generated through SEM will not show the binding statement, though the create default statement is generated.

WORKAROUND

Use the Transfer Manager or Object Manager in SQL Server version 4.21 to generate scripts. The relevant default binding statements can then be "cut and pasted" onto the script generated by the SQL Enterprise Manager.

Alternately, you could manually add the default binding statements.

STATUS

Microsoft has confirmed this to be a problem in 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.

Additional query words: sql6 scripts batch
Keywords : kbbug6.00 kbfix6.00.sp3 kbusage SSrvEntMan SSrvTran_SQL
Version : 4.21 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 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.