Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-04-25 : 22:16:52
|
Kevin writes "With Windows NT Authentication, when a user in a group defined as 'developer' with db_owner database role membership in SQL Server 7 creates an object (table, stored procedure, etc.) the object is assigned an owner that is not a user in the database. The user is in a different database and this causes SQL Server to issue a error message that the object does not exist in the system catalog.
Using:
select *
from sysobjects
where name = 'tablename'
The object and its user uid can be found but...
Using:
select *
from sysusers
The user will not exist in the database.
Until the user is added to the database nothing can be done.
Once the user is added, the user can drop the object.
When a user in a group defined as 'administrator'with system administrator server role membership in SQL Server 7 creates an object, the object is assigned an owner of 'dbo' which is what is wanted in both cases. Any advice?" |
|
|
|
|
|
Object Ownership With Windows NT Authentication