Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 35.1Mb
PDF (A4) - 35.2Mb
Man Pages (TGZ) - 256.4Kb
Man Pages (Zip) - 361.2Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
Excerpts from this Manual

MySQL 5.7 Reference Manual  / ...  / MySQL NDB Cluster 7.5 and NDB Cluster 7.6  / NDB Cluster Overview  / Known Limitations of NDB Cluster  /  Limits Associated with Database Objects in NDB Cluster

21.2.7.5 Limits Associated with Database Objects in NDB Cluster

Some database objects such as tables and indexes have different limitations when using theNDBCLUSTER storage engine:

  • Database and table names.  When using theNDB storage engine, the maximum allowed length both for database names and for table names is 63 characters. A statement using a database name or table name longer than this limit fails with an appropriate error.

  • Number of database objects.  The maximum number ofallNDB database objects in a single NDB Cluster—including databases, tables, and indexes—is limited to 20320.

  • Attributes per table.  The maximum number of attributes (that is, columns and indexes) that can belong to a given table is 512.

  • Attributes per key.  The maximum number of attributes per key is 32.

  • Row size.  The maximum permitted size of any one row is 14000 bytes.

    EachBLOB orTEXT column contributes 256 + 8 = 264 bytes to this total; this includesJSON columns. SeeString Type Storage Requirements, as well asJSON Storage Requirements, for more information relating to these types.

    In addition, the maximum offset for a fixed-width column of anNDB table is 8188 bytes; attempting to create a table that violates this limitation fails with NDB error 851Maximum offset for fixed-size columns exceeded. For memory-based columns, you can work around this limitation by using a variable-width column type such asVARCHAR or defining the column asCOLUMN_FORMAT=DYNAMIC; this does not work with columns stored on disk. For disk-based columns, you may be able to do so by reordering one or more of the table's disk-based columns such that the combined width of all but the disk-based column defined last in theCREATE TABLE statement used to create the table does not exceed 8188 bytes, less any possible rounding performed for some data types such asCHAR orVARCHAR; otherwise it is necessary to use memory-based storage for one or more of the offending column or columns instead.

  • BIT column storage per table.  The maximum combined width for allBIT columns used in a givenNDB table is 4096.

  • FIXED column storage.  NDB Cluster 7.5 and later supports a maximum of 128 TB per fragment of data inFIXED columns. (Previously, this was 16 GB.)