The OWNERSHIP privilege is unique in that it must be granted by one role to another and cannot be revoked.
This ensures that the transfer of ownership is deliberate and permanent, reflecting the importance of ownership in managing access and permissions.

The ACCESS_HISTORY view in the SNOWFLAKE.ACCOUNT_USAGE schema contains information about the access history of Snowflake objects, such as tables and views, within the last 365 days1.

The command used to export or unload data from Snowflake to a stage (such as a file in an S3 bucket, Azure Blob Storage, or Google Cloud Storage) is the PUT command. The PUT command is designed to upload data files from a local file system (in the case of SnowSQL or other client) or a virtual warehouse to a specified stage. This functionality is critical for scenarios where data needs to be extracted from Snowflake for use in external systems, backups, or further processing.
The syntax for the PUT command follows the structure: PUT file://<local_file_path> @<stage_name>, where <local_file_path> specifies the path to the file(s) on the local file system that you wish to upload, and <stage_name> specifies the destination stage in Snowflake.
It's important to distinguish that the PUT command is used for exporting data out of Snowflake, whereas the COPY INTO <table> command is used for importing data into Snowflake from a stage. The GET command, on the other hand, is used to download files from a stage to the local file system, essentially the inverse operation of the PUT command.
Reference:
Snowflake Documentation on Loading and Unloading Data: [Loading and Unloading Data](https://docs.snowflake.com/en/user-guide/data-load

* Masking policies in Snowflake require a minimum of the Business Critical Edition.
* This feature enables dynamic masking of plain-text data at query time to meet compliance and security requirements.
* Example:
sql
CopyEdit
CREATE MASKING POLICY ssn_mask AS (val STRING)
RETURNS STRING ->
CASE
WHEN CURRENT_ROLE() IN ('DATA_ANALYST') THEN '***-**-****'
ELSE val
END;
References:
* Snowflake Documentation: Dynamic Data Masking
* Snowflake Editions Comparison