Tablestore limits
This topic describes the limits of Tablestore.
Instances
Restrictions | Limitations | Description |
Number of instances | 10 | If your business requirements exceed this limit, submit a ticket to contact us. |
Instance name | Unique within a region | In VCU mode, instance names are generated automatically, and you can set a custom alias. In CU mode, the instance name naming conventions are as follows:
|
Number of tables in an instance | 64 | This limit includes the number of data tables, secondary index tables, time series tables, Lastpoint index tables, and analytics stores. If your business requirements exceed this limit, submit a ticket to contact us. Important A time series table uses two table quotas because it includes a timeline metadata table and a timeline data table. |
Wide table model
Limitations | Limit | Description |
Data table name | Unique within an instance | The naming conventions for data tables are as follows:
|
Number of primary key columns | 1 to 4 | The first primary key column is the partition key. |
Data type of primary key columns | String, Integer, Binary |
|
Number of attribute columns | Unlimited | Tablestore does not limit the number of attribute columns. If you read a very wide row with hundreds of thousands of attribute columns at once, the operation may time out and fail. To avoid this, specify the attribute columns to read or use paging. We recommend keeping the number of attribute columns under 10,000. |
Data type of attribute columns | String, Integer, Double, Boolean, Binary |
|
Number of predefined columns | 0 to 32 | Predefined columns are non-primary key columns and their data types that are defined in advance for a data table. They can be used as fields for secondary indexes. |
For more information, see Wide table model limits.
Time series model
Limit item | Limitations | Description |
Time series table name | Unique within an instance | The naming conventions for time series tables are as follows:
|
Storage Count for Analysis | 1 | You can create a maximum of one analytics store for each time series table. |
Number of Lastpoint indexes | 10 | The total number of Lastpoint index tables and analytics stores for a time series table cannot exceed 10. |
For more information, see Time series model limits.
Search index
Limits | Limit | Description |
Number of search indexes | Unlimited | We recommend creating only one search index that includes all the fields you need to retrieve. |
Number of search index fields | 1,000 | None. |
Row count limit | 100 billion | If your business requirements exceed this limit, submit a ticket to contact us. |
Total size limit | 100 TB | If your business requirements exceed this limit, submit a ticket to contact us. |
Read/write rate | 50,000 rows/s |
If your business requirements exceed this limit, submit a ticket to contact us. |
Synchronization latency | 3s |
|
Multiple data versions | Not supported | None. |
For more information, see Search index limits.
Secondary index limits
Limit item | Limitations | Description |
Number of secondary indexes | 5 | If your business requirements exceed this limit, submit a ticket to contact us. |
Number of secondary index fields | 36 |
|
Multiple data versions | Not supported | None. |
For more information, see Secondary index limits.
SQL query limits
Limit item | Limitations | Description |
Mapping table and column names | Cannot be the same as reserved keywords | The naming conventions for table and column names are as follows:
|
One-time execution timeout | 30 s | The execution time of a single SQL statement depends on its complexity and the data volume in the table. The maximum execution time is 30 seconds. If the execution time exceeds this limit, the system returns an error. |
Data volume for a one-time scan | 128 MB or 100,000 rows | The maximum number of rows for a single scan is 100,000, and the maximum data size is 128 MB. If a scan exceeds these limits, the system returns an error. |
For more information, see SQL query limits.