Shadab Shah (12/31/2012)
I am new in Administration group. I read over internet that user that are created using windows auhentication have all the database rights Creating a SQL Server 2008 Database Account By Mike Chapple
. Which i thing is not correct, because i have a windows authentication account but i cannot execute DMV's. To check this i thought of creating a temp user account on a local dev server.
I think I see the language in the article that may have led you to believe that, but it is not the case and not what the author was trying to say.
In Windows authentication mode, you assign all database permissions to Windows accounts.
Does not mean that all SQL Server logins that are based on Windows Accounts have "all database permissions." It mean that when you create a SQL Server login based on a Windows Account that all permissions granted to the SQL Server login are in essence attached to the Windows Account. A subtle distinction, but an important one. Make sense?
You still must grant SQL Server permissions to the SQL Server login. The fact this it is based on a Windows Account does not afford it any additional permissions over a login that utilizes SQL Server Authentication.
I tried to create a account with windows authentication but did not get where to set the DMV's permission to the user.(I though of DMV's because my actual DEV account is without the access to DMV's ).
Now i want to know how to set the Different permission for the user we are creating.
Which DMVs are you trying to grant access too? In general granting the server-level permission VIEW SERVER STATE allows the use of many of the DMOs (Dynamic Management Objects > includes DMVs and DMFs).
__________________________________________________________________________________________________There are no special teachers of virtue, because virtue is taught by the whole community. --Plato