Skip to content

Latest commit

 

History

History
59 lines (53 loc) · 3.27 KB

File metadata and controls

59 lines (53 loc) · 3.27 KB
title sys.security_predicates (Transact-SQL) | Microsoft Docs
ms.custom
SQL2016_New_Updated
ms.date 06/10/2016
ms.prod sql-non-specified
ms.reviewer
ms.suite
ms.technology
database-engine
ms.tgt_pltfrm
ms.topic language-reference
applies_to
Azure SQL Database
SQL Server 2016 Preview
f1_keywords
SYS.SECURITY_PREDICATES
SECURITY_PREDICATES
SECURITY_PREDICATES_TSQL
SYS.SECURITY_PREDICATES_TSQL
dev_langs
TSQL
helpviewer_keywords
sys.security_predicates catalog view
security_predicates catalog view
ms.assetid c7a2f28c-98da-463d-8b8a-8e5619e2c6a6
caps.latest.revision 9
author BYHAM
ms.author rickbyh
manager jhubbard

sys.security_predicates (Transact-SQL)

[!INCLUDEtsql-appliesto-ss2016-asdb-xxxx-xxx_md]

Returns a row for each security predicate in the database.

Column name Data type Description
object_id int ID of the security policy that contains this predicate.
security_predicate_id int Predicate ID within this security policy.
target_object_id int ID of the object on which the security predicate is bound.
predicate_definition nvarchar(max) Fully qualified name of the function that will be used as a security predicate, including the arguments. Note that the schema.function name may be normalized (i.e. escaped) as well as any other element in the text for consistency. For example:

[dbo].[fn_securitypredicate]([wing], [startTime], [endTime])
predicate_type int The type of predicate used by the security policy:

0 = FILTER PREDICATE

1 = BLOCK PREDICATE
predicate_type_desc nvarchar(60) The type of predicate used by the security policy:

FILTER

BLOCK
operation int The type of operation specified for the predicate:

NULL = all applicable operations

1 = AFTER INSERT

2 = AFTER UPDATE

3 = BEFORE UPDATE

4 = BEFORE DELETE
operation_desc nvarchar(60) The type of operation specified for the predicate:

NULL

AFTER INSERT

AFTER UPDATE

BEFORE UPDATE

BEFORE DELETE

Permissions

Principals with the ALTER ANY SECURITY POLICY permission have access to all objects in this catalog view as well as anyone with VIEW DEFINITION on the object.

See Also

Row-Level Security
sys.security_policies (Transact-SQL)
CREATE SECURITY POLICY (Transact-SQL)
Security Catalog Views (Transact-SQL)
Catalog Views (Transact-SQL)
Principals (Database Engine)