Introduction min read

SingleStore Managed Service is the on-demand managed service version of SingleStore DB v7.3. It provides the same functionality, capabilities, ingest and query performance, scalability, and resiliency available through self-managed SingleStore DB clusters while handling all installation-, operation- and management-related details.


To learn more about SingleStore Managed Service, please visit the SingleStore Managed Service introduction and take the self-paced training course.

Use this guide to learn more about deploying and using your own SingleStore Managed Service cluster.

Columnstore as Default

The default_table_type engine variable specifies whether CREATE TABLE creates a default rowstore or columnstore table. In SingleStore Managed Service, the default is set to columnstore for newly created v7.3 clusters only. For existing clusters, this variable remains as rowstore.

While the “columnstore as default” feature now creates columnstore tables by default via the standard CREATE TABLE syntax, you may also create a rowstore table explicitly via the CREATE ROWSTORE TABLE ... syntax, regardless of the setting of default_table_type.

Associated Changes

Hash Keys and Sort Keys

A standard CREATE TABLE statement using KEY(<k>) stores <k> as a hash key in the resulting columnstore table.

Hash keys support fast equality lookups, but not fast range filters. To create an index to help support fast range filters on a columnstore table, a sort key <sk> can be used by explicitly specifying KEY(<sk>) USING CLUSTERED COLUMNSTORE in your CREATE TABLE statement.

Ordered Index

Using more than one ordered index is no longer supported. Effectively, a table may only have one, which is the columnstore sort key.

Multi-column Unique Keys not Supported

Using multi-column unique keys in a columnstore table is not supported and will result in an error.

Composite Keys

Lookups of a composite key may now take longer. For example, instead of seeking on one index KEY(a,b), the KEY(a) index and the KEY(b) index must both be searched, and the key sets must then be intersected to determine which rows to look up.

Additional Information

Refer to Creating a Columnstore Table Using Standard CREATE TABLE Syntax for additional information.