Schema change breaks permissions on linked server

[RRinTetons]

I have an existing DB on a linked server that is referenced in sp's in a db on the local server. I've always just left things in the dbo schema, but it's getting messy enough that I want to create a new schema to better control/organize objects on the local server. I try to recompile an sp in the new schema I get errors from the linked server complaining about permissions on objects in its database. It's seems like my new schema on the local server isn't legal on the linked server, but I can't find any reference to it anyplace to correct.

What needs to be changed, and where do I change it?

-
Richard Ray
Jackson Hole Mountain Resort

 

[SQLBill]

DBO schema was created for a reason. It is a schema that can be access by anyone, on any database, on any SQL Server server.

When a different schema is created it only has access to its own objects unless you specifically state dbo.<object name>. For example. Let's say I create a schema SQLBill. SQLBill only has access to those objects owned by SQLBill, such as SQLBill.mytable, SQLBill.myfunction. No one else but me has access to my schema unless I specifically grant it to them and then they have to call any object by using the SQLBill.<object name> coding. If I am using the SQLBill schema, I don't have to use SQLBill.mytable, it is taken for granted and if mytable doesn't exist in the SQLBill schema, it will look for it in the DBO schema.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875