Hi
I've created a stored procedure prUpdProduct on dbProduct that updates a table Brochure on dbBrochure which in turn has an on insert, update trigger trBrochure that updates another table BrochureFeature on dbBrochure.
I have granted UserApp execute permission to prUpdProduct but it breaks when it encounters trBrochure. I assume the ownership chain is broken even though the server (SP3) is set to allow cross database ownership chaining and this is set to ON on both dbProduct and dbBrochure.
Running sphelp reveals prUpdProduct,Brochure and BrochureFeature are owned by dbo which is user sa with identical SID 0x01 on both databases.
I am at a loss to understand why this doesnt work, and could grant insert, update perms to UserApp on BrochureFeature but would prefer to use ownership chaining if this is possible.
Any ideas ?
Life is a blast when you have a semi-automatic..
I've created a stored procedure prUpdProduct on dbProduct that updates a table Brochure on dbBrochure which in turn has an on insert, update trigger trBrochure that updates another table BrochureFeature on dbBrochure.
I have granted UserApp execute permission to prUpdProduct but it breaks when it encounters trBrochure. I assume the ownership chain is broken even though the server (SP3) is set to allow cross database ownership chaining and this is set to ON on both dbProduct and dbBrochure.
Running sphelp reveals prUpdProduct,Brochure and BrochureFeature are owned by dbo which is user sa with identical SID 0x01 on both databases.
I am at a loss to understand why this doesnt work, and could grant insert, update perms to UserApp on BrochureFeature but would prefer to use ownership chaining if this is possible.
Any ideas ?
Life is a blast when you have a semi-automatic..