Cross-database ownership with different dbo
From: Aidar (aidar_at_onyx-pharm.ru)
Date: 08/29/03
- Next message: Roy Goldhammer: "Allowing Server to work with Trust connection"
- Previous message: Tino Uhlig: "SSL encryption"
- Next in thread: Dejan Sarka: "Re: Cross-database ownership with different dbo"
- Reply: Dejan Sarka: "Re: Cross-database ownership with different dbo"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 29 Aug 2003 11:47:13 +0400
We have several databases within a single instance of SQL Server SP3a.
Cross-database ownership is enabled for the instance. If we look into
'Users' container in Enterprise Manager we can see, that in most databses
[dbo] user does not have a corresponding login (the field is blank).
Cross-databse ownership works fine between these databases.
Recently I have greated a new database [Assets]. In this database user [dbo]
has a corresponding login - "DOMAIN\aidar" - member of [sysadmin] fixed
role. The cross-database ownership does not work between [Assets] and other
databases.
It seems, that SQL Server thinks, that these databases have different
owners.
Does anybody know, in which cases SQL Server creates databases with blank
login corresponding to [dbo] user, and in which cases it assigns login of
current user to [dbo] user?
What is the best way to enable cross-database ownership in this case:
manually delete corresponding login from [dbo] user in database [Assets] or
assign my login "DOMAIN\aidar" to [dbo] user in each database that
participates in cross-database ownership?
Thanks for any answer.
- Next message: Roy Goldhammer: "Allowing Server to work with Trust connection"
- Previous message: Tino Uhlig: "SSL encryption"
- Next in thread: Dejan Sarka: "Re: Cross-database ownership with different dbo"
- Reply: Dejan Sarka: "Re: Cross-database ownership with different dbo"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
