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

ID Number: Q69360

1.10 1.11 4.20

OS/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 SAF and create another user named

CROSS with the password "country."

6. Use the administrative menu of SAF to assign the user CROSS the

alias of DBO for the WATER database.

7. Open a third screen group, log onto SQL Server via SAF, 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.

Additional reference words: Security and permissions