Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am a SQL Server newbie and would really appreciate any help.

I have created a new login (test2) with sql server authentication and granted select & vierw definition permission on another schema (test1) to test2. I am however not able to see the objects of test1 in the object explorer. However I can select the objects from the Query Window.

Since this new login is being used to develop reports the user would like to view the objects in the Object Explorer.

Another user test3 created using windows authentication and similar permissions is able to see test1's objects in the explorer.

Please let me if this is the cause and if not how can help test2 see the objects in Object Explorer.

share|improve this question

migrated from Jun 30 '10 at 15:13

This question came from our site for professional and enthusiast programmers.

It may be that the Windows login belongs to a group like Administrators, and that Administrators group may have more permissions granted to it in SQL Server. This will show up as something like "BUILTIN\Administrators" under Security->Logins. This would explain the difference in the bahaviors if this is the case. As to what permissions you need to add to the sql login, I'm not sure cause Management Studio is picky in that sometimes you have to give extra permissions even though they shouldn't be needed. – AaronLS Jun 28 '10 at 18:51

Thanks guys. I found a workaround. Apparently this is a bug in 2008. I grnnated view definition permission on the database (as opposed to schema) to the user and he is able to see them now.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.