[dba-SQLServer]cross database ownership?

I have that but it still doesn't resolve when the user is only a member 
of one database
it's not until I make them members of the 2nd database that it does it 
right.

-- 
-Francisco




Mike & Doris Manning wrote:

>I get around this by referencing the table in db2 from sprocs in db1.
>
>The syntax for referencing a table in another database is:
>Database.dbo.table
>
>The syntax for referencing a field in a table in another database is:
>Database.dbo.table.field
>
>
>Doris Manning
>Database Administrator
>Hargrove Inc.
>www.hargroveinc.com
>
>
>-----Original Message-----
>From: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco H
>Tapia
>Sent: Wednesday, February 04, 2004 8:34 PM
>To: SQL Server 2k List; dba-SQLServer at databaseadvisors.com
>Subject: [dba-SQLServer]cross database ownership?
>
>
>How the heck does this work... I'm very puzzled.. I have SQL2000 w/ SP3 
>and i'm realy grasping at straws right now as I can't seem to find the 
>easiest solution for this...
>
>
>I have an NT group in a role who has rights to sprocs on my database, 
>They have execute rights but no table rights... however the sproc looks 
>for data which spans across 2 databases
>
>It does not make sense to me that I can't access the data in database 2 
>especially since cross database ownership is turned on, on both databases.
>
>the sproc is created by dbo, is there something else I need to do?  SO 
>in the mean time I've added the user into both databases and into roles 
>by the same name.. db_myRole in db1 and db_myRole in db2
>
>now I get an error stating that the user dosen't have select rights on 
>db2... this shouldn't be.for testing I gave the role rights to the table 
>and still nothing
>any ideas?  am I using cross database ownership wrong?  I'm about ready 
>to yank the table into the first database.
>
>  
>