Announcing storage controls for schemas in Amazon Redshift
You can now restrict the amount of disk space used by a schema in Amazon Redshift. With the CREATE and ALTER SCHEMA statement, administrators can set quotas on the maximum amount of storage consumed by schemas.
You can now restrict the amount of disk space used by a schema in Amazon Redshift. With the CREATE and ALTER SCHEMA statement, administrators can set quotas on the maximum amount of storage consumed by schemas.
As many organizations move towards self-service analytics, there is a need to enforce data governance and cost controls on the amount of data consumed by end users. With storage controls for schemas, Amazon Redshift empowers data analytics leaders to control and monitor the amount of storage used by different applications and users across an organization.
You can alter schema quotas at any time. The disk space used by a schema is measured as the collective disk used by all permanent tables and materialized views. When a transaction exceeds the quota, Amazon Redshift aborts the transaction and prohibits subsequent ingestion. When a transaction is aborted, an error message appears describing the specific schema name and quota that was exceeded. You can still run commands like DROP and VACUUM even when the schema exceeds an assigned quota. Use SVV_SCHEMA_QUOTA_STATE and STL_SCHEMA_QUOTA_VIOLATIONS system tables to monitor schema size and quota consumption.
Storage controls for schemas are enabled by default with the release version 1.0.14677 or later in the AWS Regions where Amazon Redshift is available. For more information, see the documentation and the blog. Refer to the AWS Region Table for Amazon Redshift availability.