BUG: Security Manager Not Remove Aliases When Revoking Logins

Last reviewed: April 29, 1997
Article ID: Q113401

The information in this article applies to:

  - Microsoft SQL Server version 4.2

BUG# NT: 9957 (4.2)

SYMPTOMS

SQL Security Manager does not remove aliases to any database for a system login when it is being revoked. This can cause a problem when the system login id being dropped is the last login id in syslogins; because after the login is dropped, the next system login added will be automatically aliased to the databases the dropped login was aliased to.

WORKAROUND

After the system login id has been deleted, drop the alias from the database manually using SP_DROPALIAS.

STATUS

Microsoft has confirmed this to be a problem in SQL Security Manager version 4.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 SSrvWinNT
Version : 4.2 4.21
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 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.