<classification_profile_name>!SET_CLASSIFY_VIEWS¶
Specifies whether to classify views during sensitive data classification.
Syntax¶
<classification_profile_name>!SET_CLASSIFY_VIEWS( <boolean_value> )
Arguments¶
boolean_value
Specifies whether to enable classification of views for the instance of the CLASSIFICATION_PROFILE class.
TRUE enables the classification of views.
FALSE disables the classification of views. Only tables will be classified by sensitive data classification.
Default: FALSE
Access control requirements¶
A role used to execute this operation must have the following privileges at a minimum:
Instance role |
Object |
Notes |
---|---|---|
|
The classification profile instance. |
The account role that calls this method must be granted this instance role on the classification profile. The role used to create the instance is automatically granted this instance role. |
The USAGE privilege on the parent database and schema are required to perform operations on any object in a schema.
For instructions on creating a custom role with a specified set of privileges, see Creating custom roles.
For general information about roles and privilege grants for performing SQL actions on securable objects, see Overview of Access Control.
Usage notes¶
Calling this method does not return the object. Because of this, you can’t use method chaining to call another method on the return value of this method. Instead, call each method in a separate SQL statement.
Examples¶
Configure the classification profile so that views are classified along with tables:
CALL my_classification_profile!SET_CLASSIFY_VIEWS(true);
Disable view classification for the classification profile:
CALL my_classification_profile!SET_CLASSIFY_VIEWS(false);