A security principal is an identity that uses SQL Server and can be granted permission to access and modify data. Principals can be individuals, groups of users, roles or entities that are treated as people (such as dbowner, dbo or sysadmin).
Security principals can be created and managed in two ways:
SQL Server Management Studio (SSMS) — This environment is built for managing various SQL infrastructures, including SQL Server and Azure SQL Database. SMSS provides tools for:
SQL Server and database configuration, monitoring, and instance administration
Deploying, monitoring, and upgrading data-tier application components
Building queries and scripts
Transact-SQL (T-SQL) — This proprietary extension of SQL is central to utilizing Microsoft SQL services. All database commands provided in this article are T-SQL statements.
SQL Server supports role-based access control for security principals. Roles are similar to Microsoft Windows security groups: You define a variety of roles, assign permissions and restrictions, and add users to the server roles corresponding to their job duties. Permissions assigned to a particular role are inherited by all members of the role, so there is no need to create and manage unique permission sets for individual users.
Both server-level and database-level roles can be used.
More Info: jobs you can get with a+ certification
No comments:
Post a Comment