INF: Restricting Access to Master Database in SQL Server

Last reviewed: April 25, 1997
Article ID: Q75291

The information in this article applies to:

  - Microsoft SQL Server version 4.2 for OS/2

The GUEST username in the master database is necessary for users (other than the system administrator) to log in and should not be removed. If it is removed, a user who does not have an account in the master database can no longer log in to the server. This is the case even if the user has an account in a default database other than the master.

Because the GUEST username should not be removed, there is no way to physically restrict users from the master database. That is, they can still execute the USE MASTER command. However, if the users do not have an account in the master database, they are given access under the GUEST username. To restrict users from accessing or viewing objects, revoke privileges such as SELECT and EXECUTE from the PUBLIC group, of which GUEST is a member.

Additional query words: Security and permissions
Keywords : kbother SSrvServer
Version : 4.2
Platform : OS/2
Issue type : kbtshoot

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 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.