Thanks for that. We have other systems on the same databases at other clients. Here it is just meg scale. Unfortunately this is future planning for a client being converted...

I completely missed right click and show all, what concerns me still though is that tools Choose Toolbox items is greyed out, should it be?

Thanks, was it like this on previous versions as well? Can't remember seeing it

Forgot to add, even sysadmins cannot execute the procedures, am I right it saying sysadmins would always have execute rights even if its not been granted to them, we also...

Will try, just afraid that will give them access to what SuperUser has access to, so they would be able to actually open the database schema for example is superuser...

Anyone have any specifics I can check for?

In summary
We have a DB(call it DB2) where 3rd parties sign in with views pointing to other databases(call it DB1)...

I am a bit skeptical about impersonate permissions as they are on user level. Is impersonation not already built in in die stored procedure with the WITH EXECUTE AS?

Hi Lowell, did you read through the whole story from the beginning, Think this is what I have done. It is working perfectly on the one environment, on another on...

Will give it a try

When EXECUTE AS CALLER is specified, IMPERSONATE permissions are not required. -- This is why I wonder if you need impersonate access added to the Procedure

Added to that if I run this
select d.name, d.sid, s.name, s.sid
from sys.database_principals d
full join sys.server_principals s
on d.principal_id = s.principal_id
where d.name = 'SuperUser'

Columns...

Taken from Microsoft's EXECUTE AS page:
To specify EXECUTE AS on a login, the caller must have IMPERSONATE permission on the specified login name and must not be denied the IMPERSONATE ANY LOGIN permission. To specify EXECUTE...