SingleStore

Author: s | 2025-04-25

Download SingleStore Ops to get up and running on SingleStore Community Edition or SingleStore Enterprise Edition today. SingleStore Ops downloads and upgrades are available for free to all SingleStore Community and Enterprise users. Here are some of the features in the new SingleStore Ops release: SingleStore (MemSQL) You can find out more about the SingleStore database at the SingleStore home page . SingleStore is syntactically a MySQL variant, and you can use actions like the MySQL bulk loader with SingleStore.

Why SingleStore: SingleStore Helios In

Direction Description TCP 22 Inbound and Outbound For host access. Required between nodes in SingleStore tool deployment scenarios. Also useful for remote administration and troubleshooting on the main deployment host. TCP 443 Outbound To get public repo key for package verification. Required for nodes downloading SingleStore APT or YUM packages. TCP 3306 Inbound and Outbound Default port used by SingleStore. Required on all nodes for intra-cluster communication. Also required on aggregators for client connections. The service port values are configurable if the default values cannot be used in your deployment environment. For more information on how to change them, see: The cluster file template provided in this guide The SingleStore configuration file The sdb-toolbox-config register-host command We also highly recommend configuring your firewall to prevent other hosts on the Internet from connecting to SingleStore. Install SingleStore Tools The first step in deploying your cluster is to download and install the SingleStore Tools on one of the hosts in your cluster. This host will be designated as the main deployment host for deploying SingleStore across your other hosts and setting up your cluster. These tools perform all major cluster operations including downloading the latest version of SingleStore onto your hosts, assigning and configuring nodes in your cluster, and other management operations. For the purpose of this guide, the main deployment host is the same as the designated Master Aggregator of the SingleStore cluster. Installation - Tarball Download SingleStore Files Download the singlestoredb-toolbox, singlestore-client, and singlestoredb-server files onto the main deployment host,

The SingleStore ODBC Driver SingleStore Documentation

SingleStore is MySQL compatible and provides native software (drivers, connectors, etc.) which may provide specific enhancements to SingleStore's performance or features. The native software must be installed on the system to leverage these optimizations. SingleStore regularly releases new versions to address bugs and introduce new features. SingleStore recommends using the latest version of SingleStore drivers and connectors. SingleStore maintains a driver and connector version support policy with the following guidelines: SingleStore generally supports each driver and connector release for at least two years, except when more recent releases provide critical fixes for security or performance issues. SingleStore may not support connectivity with versions older than this. SingleStore recommends using versions released within the scope of SingleStore's support policy. SingleStore does not distribute versions that are no longer supported. Latest driver and connector releases provide performance enhancements, new features, and bug fixes. They are not retroactively made available in the older versions. For critical fixes, SingleStore may require updating the driver or connector to the latest version or a version higher than the oldest supported version. This policy does not apply to drivers and connectors provided by third-party companies outside of SingleStore's control. Contact the respective third-party provider for their latest support policies.

SingleStore Self-Managed SingleStore Documentation

Not applicable SingleStore 7.3.9 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.3.10 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.3.11 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.3.12 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.3.13 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.5.6 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.5.7 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.5.8 server MariaDB JDBC driver version 2.7.3 Not applicable SAP HANA 2.0 SP05 server SAP Hana JDBC driver version 2.0.SP5 Not applicable TIBCO Composite Server 8.4 Tibco Composite JDBC driver version 8.4.0 Not applicable Mongo BI Connector Server 2.14.3 MySQL JDBC driver version 5.1.47 Not applicable Vertica 11.0.0 server Vertica JDBC Driver 10.00.0100 Windows ODBC Driver Version 10.01 Linux-x86- ODBC Driver Version 9.2.1 Teradata 17.10 server Teradata JDBC driver version 17.10.00.14 Teradata JDBC driver version 17.10.00.17 Windows Teradata ODBC Driver Version 17.10.00.10 Linux-x86-Teradata ODBC Driver Version 17.10.00.10 IBM Db2 iSeries JT400 Server 7.4 JTOpen JDBC Driver 10.6 Windows DB2 Data Server Client 11.05.0400 Linux-x86 - DB2 Data Server Client 11.05.0400 IBM Db2 Z Server 12.1.5 IBM JCC JDBC driver version 4.29.24 Windows - DB2 Data Server Client 11.05.0400 Linux-x86- DB2 Data Server Client 11.05.0400 IBM Db2 11.5.6 server IBM JCC JDBC driver version 4.29.24 Windows DB2 Data Server Client 11.05.0400 Linux-x86-DB2 Data Server Client 11.05.0400 Dremio 17.0.0 Dremio JDBC Driver 17.0.0-202107060524010627-31b5222b Not applicable PostgreSQL Server 12.7 PostgreSQL JDBC driver version 42.2.23 Windows ODBC driver 13.01.000 Linux-x86-ODBC driver 13.02.000 PostgreSQL Server 12.8 PostgreSQL JDBC driver version 42.2.23 Windows ODBC driver 13.01.000 Linux-x86-ODBC driver 13.02.000 PostgreSQL Server 13.3 PostgreSQL JDBC driver version 42.2.19 PostgreSQL JDBC driver version 42.2.20 PostgreSQL JDBC driver version 42.2.21 PostgreSQL JDBC driver version 42.2.22 PostgreSQL JDBC driver version 42.2.23 Windows ODBC driver 13.01.000 Linux-x86-ODBC driver 13.02.000 PostgreSQL Server 13.4 PostgreSQL JDBC driver version 42.2.23 Windows ODBC driver 13.01.000 Linux-x86-ODBC driver 13.02.000 Progress DataDirect Autonomous REST JDBC driver 6.0.0.004291 Not applicable MySQL 8.0.24 server MySQL JDBC driver version 8.0.24 Windows-MySQL Connector/ODBC 8.0.26 Linux-x86-MySQL Connector/ODBC 8.0.24 MySQL 8.0.25 server MySQL JDBC driver version 8.0.25 Windows-MySQL Connector/ODBC 8.0.26. Download SingleStore Ops to get up and running on SingleStore Community Edition or SingleStore Enterprise Edition today. SingleStore Ops downloads and upgrades are available for free to all SingleStore Community and Enterprise users. Here are some of the features in the new SingleStore Ops release:

About SingleStore Pipelines SingleStore Documentation

Or onto a device with access to the main deployment host. To obtain the latest version of each file, use the following: curl Replace with memsqltoolbox, memsqlclient, and singlestoredbserver to download the list of available file types. To download the latest patch release of a major version, substitute the desired major version for latest. For example: curl To download a specific patch release of a major version, substitute the desired patch release for latest. For example: curl The JSON you receive contains relative file paths in the following format: "Path": "production/tar/x86_64/--.x86_64.tar.gz" Use wget to download the file by copying, pasting, and appending the path (minus the quotes) to Examples are shown below. wget Alternatively, download the following SingleStore tarball files onto a device with access to the main deployment host. Transfer SingleStore Files Transfer the singlestoredb-toolbox, singlestore-client, and singlestoredb-server tarball files into a dedicated singlestore directory that has been configured so that non-sudo users can access on the main deployment host, such as /opt/singlestore. Unpack SingleStore Files Note: For the remainder of this document, - will be written simply as . Unpack singlestoredb-toolbox and singlestore-client into the singlestore directory. tar xzvf singlestoredb-toolbox-version>.tar.gz && \tar xzvf singlestore-client-version>.tar.gz You do not need to unpack the singlestoredb-server file in this step. It will be installed as part of deployment, which is shown in the next step. Deploy SingleStore Prerequisites Warning Before deploying a SingleStore cluster in a production environment, please review and follow the host configuration recommendations. Failing to follow these recommendations will

SingleStore Toolbox Installation SingleStore Documentation

Result in sub-optimal cluster performance. In addition, SingleStore recommends that each Master Aggregator and child aggregator reside on its own host when deploying SingleStore in a production environment. Notes on Users and Groups The user that deploys SingleStore via SingleStore Toolbox must be able to SSH to each host in the cluster. When singlestoredb-server is installed via an RPM or Debian package when deploying SingleStore, a memsql user and group are also created on each host in the cluster. This memsql user does not have a shell, and attempting to log in or SSH as this user will fail. The user that deploys SingleStore is added to the memsql group. This group allows most Toolbox commands to run without sudo privileges, and members of this group can perform many Toolbox operations without the need to escalate to sudo. Users who desire to run SingleStore Toolbox commands must be added to the memsql group on each host in the cluster. They must also be able to SSH to each host. Manually creating a memsql user and group is only recommended in a sudo-less environment when performing a tarball-based deployment of SingleStore. In order to run SingleStore Toolbox commands against a cluster, this manually-created memsql user must be configured so that it can SSH to each host in the cluster. Minimal Deployment SingleStore has been designed to be deployed with at least two nodes: A Master Aggregator node that runs SQL queries and aggregates the results, and A single leaf node, which

Upgrade to SingleStore 8.9 SingleStore Documentation

The cluster file. Run the following from the singlestoredb-toolbox directory with the path to the cluster file as input. ./sdb-deploy setup-cluster --cluster-file /path/to/cluster-file> Create the memsql.service File By creating the following memsql.service file and enabling the memsql service, all nodes on a host will be restarted after the host is rebooted. Performing the following steps on each host in the cluster. Create a memsql.service file in the /etc/systemd/system directory. sudo vi /etc/systemd/system/memsql.service Using the following example, replace the directory in the ExecStart and ExecStop lines with the directory in which the memsqlctl file resides on the host. In this example, the directory is /opt/singlestore/singlestoredb-server. [Unit]Description=SingleStoreAfter=network.target[Service]Type=oneshotRemainAfterExit=yesExecStart=/opt/singlestore/singlestoredb-server/memsqlctl start-node --yes --allExecStop=/opt/singlestore/singlestoredb-server/memsqlctl stop-node --yes --allSlice=system-memsql.sliceTasksMax = 128000LimitNICE=-10LimitNOFILE=1024000LimitNPROC=128000[Install]WantedBy=multi-user.target Ensure that this file is owned by root. sudo chown root:root /etc/systemd/system/memsql.service Set the requisite file permissions. sudo chmod 644 /etc/systemd/system/memsql.service Enable the memsql service to start all of the nodes on the host after the host is rebooted. sudo systemctl enable memsql.serviceCreated symlink from /etc/systemd/system/multi-user.target.wants/memsql.service to /etc/systemd/system/memsql.service. Additional Deployment Options NoteIf this deployment method is not ideal for your target environment, you can choose one that fits your requirements from the Deployment Options. Connect to Your Cluster The singlestore-client package contains is a lightweight client application that allows you to run SQL queries against your database from a terminal window. After you have installed singlestore-client, use the singlestore application as you would use the mysql client to access your database. For more connection options, help is available through singlestore --help. singlestore -h Master-or-Child-Aggregator-host-IP-address> -P port> -u. Download SingleStore Ops to get up and running on SingleStore Community Edition or SingleStore Enterprise Edition today. SingleStore Ops downloads and upgrades are available for free to all SingleStore Community and Enterprise users. Here are some of the features in the new SingleStore Ops release: SingleStore (MemSQL) You can find out more about the SingleStore database at the SingleStore home page . SingleStore is syntactically a MySQL variant, and you can use actions like the MySQL bulk loader with SingleStore.