Skip to content

securables.md

Latest commit

 

History

History
126 lines (79 loc) · 4.42 KB

securables.md

File metadata and controls

126 lines (79 loc) · 4.42 KB
title Securables | Microsoft Docs
ms.custom
SQL2016_New_Updated
ms.date 10/18/2016
ms.prod sql-server-2016
ms.reviewer
ms.suite
ms.technology
database-engine
ms.tgt_pltfrm
ms.topic article
f1_keywords
sql13.swb.roleproperties.selectobject.f1
helpviewer_keywords
securables [SQL Server]
schemas [SQL Server], securables
database securables [SQL Server]
hierarchies [SQL Server], securables
server securables [SQL Server]
ms.assetid bfa748f0-70b0-453c-870a-04b7b205b9ff
caps.latest.revision 41
author BYHAM
ms.author rickbyh
manager jhubbard

Securables

[!INCLUDEtsql-appliesto-ss2008-all_md]

Securables are the resources to which the [!INCLUDEssDEnoversion] 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.

Securable scope: Server

The server securable scope contains the following securables:

  • Availability group

  • Endpoint

  • Login

  • Server role

  • Database

Securable scope: Database

The database securable scope contains the following securables:

  • Application role

  • Assembly

  • Asymmetric key

  • Certificate

  • Contract

  • Fulltext catalog

  • Fulltext stoplist

  • Message type

  • Remote Service Binding

  • (Database) Role

  • Route

  • Schema

  • Search property list

  • Service

  • Symmetric key

  • User

Securable scope: Schema

The schema securable scope contains the following securables:

  • Type

  • XML schema collection

  • Object – The object class has the following members:

    • Aggregate

    • Function

    • Procedure

    • Queue

    • Synonym

    • Table

    • View

    • External Table

Controlling Access to a Securable

The entity that receives permission to a securable is called a principal. The most common principals are logins and database users. Access to securables is controlled by granting or denying permissions, or by adding logins and users to roles which have access. For information about controlling permissions, see GRANT (Transact-SQL), REVOKE (Transact-SQL), DENY (Transact-SQL), sp_addrolemember (Transact-SQL), and sp_droprolemember (Transact-SQL).

Caution

The default permissions that are granted to system objects at the time of setup are carefully evaluated against possible threats and need not be altered as part of hardening the [!INCLUDEssNoVersion] installation. Any changes to the permissions on the system objects could limit or break the functionality and could potentially leave your [!INCLUDEssNoVersion] installation in an unsupported state.

Related Content

Getting Started with Database Engine Permissions

Securing SQL Server

sys.database_principals (Transact-SQL)

sys.database_role_members (Transact-SQL)

sys.server_principals (Transact-SQL)

sys.server_role_members (Transact-SQL)

sys.sql_logins (Transact-SQL)