BUG: DMO Script() Method Generates GO Following CREATE INDEX

Last reviewed: March 10, 1997
Article ID: Q147391
6.00 WINDOWS kbprg kbbug6.00

The information in this article applies to:

  • Microsoft SQL Server, version 6.0

BUG# NT: 13192 (6.00)

SYMPTOMS

When you use the DMO Script() method to generate scripts for indexes (option SQLOLEScript_Indexes), the script will contain the current command terminator following each CREATE INDEX statement, even if the SQLOLEScript_NoCommandTerm script option is being used.

WORKAROUND

Change the CommandTerminator property of the SQLServer object to an empty string while scripting indexes, then change it back to its previous value after completed.

STATUS

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

MORE INFORMATION

The SQL Server object exposes the CommandTerminator property that can be read or changed using the appropriate Get or Set function. To read the current setting, use GetCommandTerminator(); to set the property, use SetCommandTerminator(). Consult the topic 'Using Property Values' in SQL Server 6.0 "Books Online" for more information on getting and setting properties. Function prototypes are available in the header file SQLOLE.H.


Additional reference words: 6.00 sql6 GO batch
KBCategory: kbpg kbbug6.00
KBSubcategory: ssrvdmo ssrvprog

Keywords : ssrvdmo ssrvprog kbbug6.00 kbprg
Version : 6.00
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: March 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.