How can I get a copy of SingleStore?

Sign into our Cloud Portal and use the free license to test out SingleStore. We offer:

• A 30-Day Free Enterprise Trial (trial key available through the Cloud Portal).

• A license that allows free use of SingleStore up to four license units.

Does SingleStore run in the cloud?

Yes. You can run a self-managed cluster in the cloud, or use our SingleStore.

Does SingleStore run on Windows?

Yes, the SingleStore Quick Start cluster-in-a-box packaged via Docker can run on Windows. A SingleStore cluster-in-a-box is a SingleStore master aggregator and leaf node collocated on a single host. This configuration is intended to provide familiarity with SingleStore but is not recommended for production.

SingleStore production environments run on modern 64-bit Linux versions, as described in the System Requirements and Recommendations section.

You can also run SingleStore on Microsoft Azure, using Azure Linux instances.

What hardware is recommended for SingleStore?

See System Requirements and Recommendations.

On which Linux distribution does SingleStore run best?

SingleStore is developed and tested most extensively on Red Hat/CentOS 6.x, 7.x, and Debian 8 and 9.

See System Requirements and Recommendations for the current list of Linux distributions that are officially supported.

How much disk space should I allocate for SingleStore?

SingleStore uses disk for three types of storage:

• Snapshot and log files that backup row store data. You should allocate about as much space on disk for this purpose as memory on your machine.

• Compressed columnstore data files that contain column store data in SingleStore.

• Object files that are the result of code generation. This includes for Data Definition Language (DDL) queries like CREATE TABLE and ALTER TABLE and for Data Manipulation Language (DML) queries like INSERT, UPDATE, DELETE and SELECT. On average, these usually require about 0.1 MB per unique plan.

Therefore, you should allocate roughly the amount of memory on your machine + space for compressed column store data + 0.1 MB for each plan. Note that the exact disk requirements will vary with the application, so it is advisable (and usually cheap) to allocate some extra disk space.

What happens if I run out of memory?

If the amount of memory used by row store tables (Alloc_table_memory from SHOW STATUS EXTENDED) is greater than the maximum_table_memory global variable (from SHOW GLOBAL VARIABLES), SingleStore will refuse to start new write queries (INSERT, UPDATE and LOAD DATA). Note that DELETE queries are not affected by this limit.

If a currently running query runs out of memory, it will rollback and notify the client of the error. See Managing Memory for more information.

What happens if I run out of disk space?

If the amount of available disk space (in the <MEMSQL HOME>/data directory) is less than the minimal_disk_space global variable (from SHOW GLOBAL VARIABLES), SingleStore will refuse to start new write queries (INSERT, UPDATE and LOAD DATA). Note that DELETE queries are not affected by this limit, and the database will remain online for reads.

If a currently running write query exhausts the available disk space before making its changes durable, it will wait until more disk space becomes available before continuing. Queries may appear to hang when this happens. To determine how many queries and background threads are waiting for disk space run SHOW STATUS EXTENDED LIKE 'Threads_waiting_for_disk_space'.