System Limits
This section describes the 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 | Limit |
---|---|
Number of nodes |
Maximum 128 (without Vertica assistance) |
Database size |
Approximates the number of files times the file size on a platform, depending on the maximum disk configuration |
Table size |
The smaller of:
|
Row size |
32,768,000 bytes Row size is approximately the sum of its maximum column sizes, where, for example, a VARCHAR(80) has a maximum size of 80 bytes. |
Key size |
Limited only by row size |
Number of tables/projections per database |
Limited by physical RAM, as the catalog must fit in memory. |
Number of concurrent connections per node |
Default of 50, limited by physical RAM (or threads per process), typically 1024 |
Number of concurrent connections per cluster |
Limited by physical RAM of a single node (or threads per process), typically 1024 |
Number of columns per table |
1600 |
Number of rows per load |
2^63 |
Number of partitions |
1024 For details, see Partitioning Best Practices in the Administrator's Guide. |
Length for a fixed-length column |
65000 bytes |
Length for a variable-length column |
32000000 bytes |
Length of basic names |
128 bytes. Basic names include table names, column names, etc. |
Query length |
No limit |
Depth of nesting subqueries |
Unlimited in |