INF: No Conflicts Between DBO and Aliased DBO in SQL Server

Last reviewed: April 25, 1997
Article ID: Q69360

The information in this article applies to:

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

SUMMARY

If an alias has been created between a user in SQL Server and the database owner (DBO) of a database, SQL Server will allow both the original DBO and the aliased DBO to access the database at the same time.

MORE INFORMATION

Example

  1. Create a user called CANOE with the password "paddle."

  2. Grant ALL privileges to CANOE.

  3. Log onto SQL Server via ISQL with the username CANOE. This will be referred to as Screen Group A.

  4. Create a database called WATER and execute a USE WATER command to position the user CANOE into the WATER database.

  5. Open a second screen group and log onto SQL Server as the user sa (system administrator) via SQL Administrator and create another user named CROSS with the password "country."

  6. Using SQL Administrator assign the user CROSS the alias of DBO for the WATER database.

  7. Open a third screen group, log onto SQL Server via ISQL, and execute a USE WATER command to position the user CROSS into the WATER database. This will be referred to as Screen Group B.

At this point, the user CANOE, which is the DBO of the WATER database, is logged onto WATER. Also, the user CROSS, which is the aliased DBO of the WATER database, is logged onto WATER.

        Screen Group           Screen Group
            A                       B
        ___________             ___________
       |           |           |           |
       |  canoe    |           |  cross    |
       |  userid   |           |  userid   |
       |___________|           |___________|
            |                        |
              |                    |
                |   Database     |
                  ______________
                 |              |
                 |    water     |
                 |              |
                 |______________|

  • Switching back and forth between the two Screen Groups A and B, create tables and insert values. There will not be any conflicts.


  • Additional query words: Security and permissions
    Keywords : kbother SSrvServer SSrvSQL_Admin SSrvWinNT
    Version : 4.2 | 4.2
    Platform : OS/2 WINDOWS
    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.