INF: No Conflicts Between DBO and Aliased DBO in SQL Server (69360)

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     |
                    |              |
                    |______________|
   					

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