Re: EXECUTE Permissions and Cross Database

It should be set to true. It can be set on the individual database level.

--
Arnie Rowland
"To be successful, your heart must accompany your knowledge."



"MickyM" <javamick@xxxxxxxxx> wrote in message
news:1153149830.956575.279290@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
It is set to false, but it is greyed out because of the server setting
I assume. They are set to compatability level 80 if that matters.
Also, they are all set to the same thing (chaining wise) which is what
stumps me (it works from Database A but not B)

Micky

Arnie Rowland wrote:
Check the database property to allow cross database ownership chaining.



--
Arnie Rowland
"To be successful, your heart must accompany your knowledge."



"Micky McQuade" <javamick@xxxxxxxxx> wrote in message
news:1153144180.968800.32910@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have an odd situation. Here are the details:

- I have three databases (A, B, C).
- I have a user that has EXECUTE and SELECT permissions on each
database.
- I have a stored procedure in A and B that does an update in C at one
point
- The stored procedure works fine from database A, but from database B,
it gives me the following UPDATE error: UPDATE permission denied on
object 'MyTable', database 'C', schema 'dbo'
- No dynamic SQL is used
- The database owners are the same as well as the table and stored
procedure owners

Can anyone help guide me on this?

Thanks,
Micky




.

Relevant Pages

  • Re: distinct with all the columns
    ... but changing the database schema is not an option because it's an ERP ... stupid data to come out of this PROGRESS DB. ... Arnie Rowland, YACE* ... where the columns have duplicate ...
    (microsoft.public.sqlserver.mseq)
  • Re: EXECUTE Permissions and Cross Database
    ... EXEC sys.sp_configure N'cross db ownership chaining', ... Arnie Rowland wrote: ... stumps me (it works from Database A but not B) ... The stored procedure works fine from database A, but from database B, ...
    (microsoft.public.sqlserver.security)
  • Re: Damaged log file
    ... error saying that phisycal name of .ldf file is not correct. ... How can I attach only the database without the .ldf file? ... Arnie Rowland* ... to verify that you want to create a new log file, ...
    (microsoft.public.sqlserver.setup)
  • Re: Damaged log file
    ... I was suggesting that you use Explorer and Delete the log file ... Arnie Rowland* ... your heart must accompany your knowledge." ... you could attach the database without a log file. ...
    (microsoft.public.sqlserver.setup)
  • Re: EXECUTE Permissions and Cross Database
    ... stumps me (it works from Database A but not B) ... Arnie Rowland wrote: ... The stored procedure works fine from database A, but from database B, ... The database owners are the same as well as the table and stored ...
    (microsoft.public.sqlserver.security)