Table Size

This post will show how to get the compressed size of Vertica tables from column_storage and projection_storage system tables in the v_monitor schema. To get an estimated raw or uncompressed data size, see my earlier post on License Utilization.

column_storage

The following query aggregates the column_storage data to the table level. You can add column_name for more granularity. Note that empty tables will not appear in this table.

projection_storage

The following query is almost identical to the one above, except for the table name. The lowest level in this system table is the table name. Any empty tables will appear in your result.

Documentation

Related Posts

  • December 23, 2013 Identifying Slow Queries In this post, I'll show how to identify slow running query requests in Vertica. The query_requests system table in the v_monitor schema […]
  • January 24, 2014 License Utilization It's important to remain compliant with license limits and not exceed space utilization in Vertica. Space utilization for licenses are […]
  • October 23, 2013 Disk Space Utilization This post will show how to query the host_resources, disk_storage and storage_usage system tables to determine compressed disk space […]
  • December 26, 2013 Importance of Using Stream Name with Copy When using a COPY bulk load in Vertica, it's important to properly identify the load using the optional STREAM NAME parameter. This […]
  • December 19, 2013 System Resource Usage The system resource usage tables in the v_monitor schema of Vertica provide a high level summary of memory, CPU, IO and network usage. […]
  • January 4, 2014 Using Query Labels In an earlier post, I wrote about the importance of using stream names for COPY loads in Vertica. This post continues on that topic with […]

About Norbert Krupa

Norbert is a Technical Consultant and founder of vertica.tips. He is an HP Accredited Solutions Expert for Vertica Big Data Solutions. He author's his own blog at jadito.us and has written the Vertica Diagnostic Queries which aim to cover monitoring, diagnostics and performance tuning. The views, opinions, and thoughts expressed here do not represent those of the user's employer.