System limits

This section describes system limits on the size and number of objects in a Vertica database.

This section describes system limits on the size and number of objects in a Vertica database. In most cases, computer memory and disk drive are the limiting factors.

Item Maximum
Nodes 128 (without Vertica assistance)
Database size

Dependent on maximum disk configuration, approximately:

numFiles * platformFileSize

Table size

Smaller of:

  • 264 rows per node

  • 263 bytes per column

Row size

(231) -1

Row size is approximately the sum of its maximum column sizes. For example, a VARCHAR(80) has a maximum size of 80 bytes.

Key size Dependent on row size
Tables/projections per database Dependent on physical RAM, as the catalog must fit in memory.
Concurrent connections per node

Dependent on physical RAM (or threads per process), typically 1024

Default: 50

Concurrent connections per cluster Dependent on physical RAM of a single node (or threads per process), typically 1024
Columns per table/view 9800
Arguments per function call 9800
Rows per load 263
ROS containers per projection

1024

See Minimizing partitions.

Length of fixed-length column 65000 bytes
Length of variable-length column 32 MB
Length of basic names 128 bytes. Basic names include table names, column names, etc.
Query length None
Depth of nesting subqueries None in FROM, WHERE, and HAVING clauses