SHOW STORAGE LIFECYCLE POLICIES¶
Lists the storage lifecycle policies for which you have access privileges.
You can use this command to list the storage lifecycle policies in the current database and schema for the session, a specified database or schema, or your entire account.
- See also:
CREATE STORAGE LIFECYCLE POLICY , ALTER STORAGE LIFECYCLE POLICY , DESCRIBE STORAGE LIFECYCLE POLICY , DROP STORAGE LIFECYCLE POLICY
Syntax¶
SHOW STORAGE LIFECYCLE POLICIES
[ LIKE '<pattern>' ]
[ IN
{
ACCOUNT |
DATABASE |
DATABASE <database_name> |
SCHEMA |
SCHEMA <schema_name> |
<schema_name>
}
]
Parameters¶
LIKE 'pattern'Optionally filters the command output by object name. The filter uses case-insensitive pattern matching, with support for SQL wildcard characters (
%and_).For example, the following patterns return the same results:
... LIKE '%testing%' ...... LIKE '%TESTING%' .... Default: No value (no filtering is applied to the output).
[ IN ... ]Optionally specifies the scope of the command. Specify one of the following:
ACCOUNTReturns records for the entire account.
DATABASE, .DATABASE db_nameReturns records for the current database in use or for a specified database (
db_name).If you specify
DATABASEwithoutdb_nameand no database is in use, the keyword has no effect on the output.注釈
Using SHOW commands without an
INclause in a database context can result in fewer than expected results.Objects with the same name are only displayed once if no
INclause is used. For example, if you have tablet1inschema1and tablet1inschema2, and they are both in scope of the database context you've specified (that is, the database you've selected is the parent ofschema1andschema2), then SHOW TABLES only displays one of thet1tables.SCHEMA, .SCHEMA schema_nameReturns records for the current schema in use or a specified schema (
schema_name).SCHEMAis optional if a database is in use or if you specify the fully qualifiedschema_name(for example,db.schema).If no database is in use, specifying
SCHEMAhas no effect on the output.
Default: Depends on whether the session currently has a database in use:
Database:
DATABASEis the default (that is, the command returns the objects you have privileges to view in the database).No database:
ACCOUNTis the default (that is, the command returns the objects you have privileges to view in your account).
Output¶
The output of the command includes the following columns, which describe the properties and metadata of the object:
Column |
Description |
|---|---|
|
Date and time the policy was created. |
|
The name of the policy. |
|
The name of the database the policy is associated with. |
|
The name of the schema the policy uses. |
|
The type of storage lifecycle policy. |
|
The name of the role that created the policy. |
|
An optional comment that describes the policy. |
|
The type of role that the owner of the policy used to create the policy. |
|
Optional parameters added to the policy to change how the policy behaves:
|
Access control requirements¶
A role used to execute this SQL command must have at least one of the following privileges at a minimum:
Privilege |
Object |
Notes |
|---|---|---|
APPLY STORAGE LIFECYCLE POLICY |
Account |
Allows SHOW on all storage lifecycle policies in the account. |
APPLY |
Storage lifecycle policy |
Allows SHOW on the policy |
OWNERSHIP |
Storage lifecycle policy |
OWNERSHIP is a special privilege on an object that is automatically granted to the role that created the object, but can also be transferred using the GRANT OWNERSHIP command to a different role by the owning role (or any role with the MANAGE GRANTS privilege). |
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 カスタムロールの作成.
For general information about roles and privilege grants for performing SQL actions on securable objects, see アクセス制御の概要.
Usage notes¶
The command returns a maximum of ten thousand records for the specified object type, as dictated by the access privileges for the role used to execute the command. Any records above the ten thousand records limit aren't returned, even with a filter applied.
To view results for which more than ten thousand records exist, query the corresponding view (if one exists) in the Snowflake Information Schema.
Examples¶
The following example lists the storage lifecycle policies that you have the privileges to view in the PUBLIC schema of the mydb
database:
USE DATABASE mydb;
SHOW STORAGE LIFECYCLE POLICIES;
Output:
+----------------------------------------+------------------+---------------------------+-------------------------------+--------------------------+--------------+-------------------+-----------------+---------------------------+
| created_on | name | database_name | schema_name | kind | owner | comment | owner_role_type | options |
+----------------------------------------+------------------+---------------------------+-------------------------------+--------------------------+--------------+-------------------+-----------------+---------------------------+
| Fri, 23 Jun 1967 07:00:00.123000 +0000 | MY_POLICY | MYDB | PUBLIC | STORAGE_LIFECYCLE_POLICY | TESTACCOUNT | identity | ROLE | {"ARCHIVE_FOR_DAYS":null} |
| Fri, 23 Jun 1967 07:00:00.123000 +0000 | MY_SECOND_POLICY | MYDB | PUBLIC | STORAGE_LIFECYCLE_POLICY | TESTACCOUNT | identity with UDF | ROLE | {"ARCHIVE_FOR_DAYS":365} |
| Fri, 23 Jun 1967 07:00:00.123000 +0000 | MY_THIRD_POLICY | MYDB | PUBLIC | STORAGE_LIFECYCLE_POLICY | TESTACCOUNT | always true | ROLE | {"ARCHIVE_FOR_DAYS":180} |
+----------------------------------------+------------------+---------------------------+-------------------------------+--------------------------+--------------+-------------------+-----------------+---------------------------+