The meaning of the Roles in SQL Server 2008 R2
-
Today I have a question to make regarding the Roles. Just because I’m confused around this issue I’d like to ask the following questions, and please I would like to receive clear and easy understandable answers. Not deep analyze. 1.What is the Roles for a programmer? 2.What is the role of the Schemas owned by this… which related with them? 3.What is the meaning and the use for Securables in Roles 4.Why we add Users to a Role? 5.How we may handle the Roles in conjunction with to the Users, inside of a project? Thank you very much in advance.
-
Today I have a question to make regarding the Roles. Just because I’m confused around this issue I’d like to ask the following questions, and please I would like to receive clear and easy understandable answers. Not deep analyze. 1.What is the Roles for a programmer? 2.What is the role of the Schemas owned by this… which related with them? 3.What is the meaning and the use for Securables in Roles 4.Why we add Users to a Role? 5.How we may handle the Roles in conjunction with to the Users, inside of a project? Thank you very much in advance.
Lefteris Gkinis wrote:
1.What is the Roles for a programmer?
"SQL Server provides server-level roles to help you manage the permissions on a server. These roles are security principals that group other principals. Server-level roles are server-wide in their permissions scope. (Roles are like groups in the Windows operating system.)" Source[^]
Lefteris Gkinis wrote:
2.What is the role of the Schemas owned by this… which related with them?
"CREATE SCHEMA can create a schema, the tables and views it contains, and GRANT, REVOKE, or DENY permissions on any securable in a single statement." Source[^]
Lefteris Gkinis wrote:
3.What is the meaning and the use for Securables in Roles
"Securables are the resources to which the SQL Server Database Engine authorization system regulates access. For example, a table is a securable. Some securables can be contained within others, creating nested hierarchies called "scopes" that can themselves be secured. The securable scopes are server, database, and schema." Source[^]
Lefteris Gkinis wrote:
4.Why we add Users to a Role?
"Roles can simplify security administration in databases with a large number of users or with a complex security system." Source[^]
Lefteris Gkinis wrote:
5.How we may handle the Roles in conjunction with to the Users, inside of a project?
That depends on the project, and it's specific needs. There's no alternative but to read the entire thing[