INF: No Conflicts Between DBO and Aliased DBO in SQL Server
ID: Q69360
|
The information in this article applies to:
-
Microsoft SQL Server for OS/2, version 4.2
-
Microsoft SQL Server version 4.2x
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 INFORMATIONExample
- Create a user called CANOE with the password "paddle."
- Grant ALL privileges to CANOE.
- Log onto SQL Server via ISQL with the username CANOE. This will
be referred to as Screen Group A.
- Create a database called WATER and execute a USE WATER command
to position the user CANOE into the WATER database.
- 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."
- Using SQL Administrator assign the user CROSS the alias of DBO for the
WATER database.
- 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 SSrvSQL_Admin SSrvServer SSrvWinNT
Version : 4.2 | 4.2
Platform : OS/2 WINDOWS
Issue type :
|