BUG: Schema Generate Does Not Produce Aliases

Last reviewed: April 29, 1997
Article ID: Q113160

The information in this article applies to:

  - Microsoft SQL Server version 4.2 for OS/2
  - Microsoft SQL Server version 4.2

BUG# 9891 (4.2)

SYMPTOMS

Object Manager's schema generate function does not put aliases into the generated script. If a database has aliases, schema generate will not include them in its generated scripts. For example, if a site does

   use pubs
   go
   sp_addlogin testlgin, NULL, pubs, NULL
   go
   sp_addlogin tstalias, NULL, pubs, NULL
   go
   sp_adduser testlgin, testuser, testgrp
   go
   sp_addalias tstalias, testuser
   go

and then uses schema generator to generate a script with all objects, users and logins, the alias tstalias will not be included in the generated script.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 4.2 and SQL Server version 4.2b for OS/2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: Windows NT
Keywords : kbbug4.20 kbtool SSrvObj_Man SSrvWinNT
Version : 4.2b | 4.2
Platform : OS/2 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 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.