SQL Server server role

When we create a SQL Server login, our options one or more server roles must be assigned login.

Server roles (not to be confused with the database roles) can be used to manage permissions on the server. Not everyone should be assigned to the role of the server. Only advanced users, such as database administrator should specify a server role.

View server role

To view the Management Studio server role in SQL Server2014, in Object Explorer, expand the Security folder:

Screenshot of viewing server roles

SQL Server 2014 provides nine fixed server role. Was granted permission to fixed server role can not be changed.

Description nine fixed server role

The following is an explanation of the installation process server roles defined in the SQL Server2014 in:

 
 
Server Role description
sysadmin You can perform any activity in SQL Server.
serveradmin You can set the server-wide configuration options and shut down the server.
setupadmin You can add and use the Server Transact-SQL statement to remove the link. (Using SQL Server Management Suite, a member of the system administrator when needed.)
securityadmin Log in to manage their properties. They can GRANT, DENY, and REVOKE server-level permissions. They can also GRANT, DENY, and REVOKE database-level permissions, if they have access to a database. They can also reset the SQL Server login password.
processadmin You can end processes running in SQL Server instance.
dbcreator You can create, modify, delete, and restore all databases.
Desk admin You can manage disk files.
bulkadmin You can execute BULK INSERT statement.
public Each SQL Server login belongs to the public server role. When a server principal has not been granted or denied specific permissions on the protected object, the object inherits the user to grant public access. Only if you want to provide to any object on all user objects allocation of public authority. You can not change the rights of members of the public.

Some of these roles allowed to perform very specific tasks. If only a small team, is likely to only use one role of which (including the system administrator) two. If there is a big team, you can use them.

In SQL Server2014 (and SQL Server2012), you can create user-defined server roles, and add server-level permissions to a user-defined server roles.



Guess you like

Origin www.cnblogs.com/borter/p/12452722.html