April 24, 2014 at 1:52 pm
I encountered a unusual situation where a user can only see default schema in a Database.
She is a member of the fixed database role db_datareader.
I make her a member of db_owner and she can see all of the schemas.
Any ideas on how this could happen?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
April 24, 2014 at 6:23 pm
Are there any DENY permissions set on the user for the other schemas?
If they try a SELECT query on one of the other schema tables (even though they can't 'see' them - I presume this is in SSMS) is there an error message returned?
dbo can't be blocked so this might explain why they can see the schemas when you add that in.
April 24, 2014 at 6:50 pm
DouglasH (4/24/2014)
Are there any DENY permissions set on the user for the other schemas?If they try a SELECT query on one of the other schema tables (even though they can't 'see' them - I presume this is in SSMS) is there an error message returned?
dbo can't be blocked so this might explain why they can see the schemas when you add that in.
That is what I initially thought so I deleted the Users and Logins and I had the same problem.
I thought about trying to select. I have multiple users with only read permissions but I do not have this problem.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply