Connect with MySQL Client

Note

When using a third-party SQL client or development tool, you must first add a database user to log into a SingleStore Helios database.

SingleStore is wire-compliant with MySQL meaning connecting to SingleStore is as easy as connecting to a MySQL database. You may need the -u user, -h host, and -P port flags to ensure you are connecting to SingleStore properly. For example:

mysql -u admin -h svc-9be5e8a1-8a5f-4aa7-b75d-a395570828f2-ddl.aws-oregon-1.svc.singlestore.com -P 3306 --default-auth=mysql_native_password -p

Here we have -u admin to specify the login, -h svc[...] to connect to the SingleStore Helios workspace, and -p 3306 to connect on port 3306 (the default port setting). The --default-auth=mysql_native_password might be necessary to set the proper authentication.

You may also use the --prompt flag to change the prompt in the interactive session, simply to help distinguish SingleStore from MySQL:

mysql -u admin -h svc-[...].svc.singlestore.com -P 3306 --default-auth=mysql_native_password -p --prompt="singlestore> "

The output when you connect should look similar to this:

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 6
Server version: 5.5.8 MemSQL source distribution (compatible; MySQL Enterprise & MySQL Commercial)
Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
singlestore>

These commands show more information about the connection and the server:

singlestore> status
--------------
mysql  Ver 8.0.23 for osx10.15 on x86_64 (Homebrew)

Connection id:		15507
Current database:	
Current user:		admin@
SSL:			Cipher in use is AES256-SHA
Current pager:		stdout
Using outfile:		''
Using delimiter:	;
Server version:		5.5.58 MemSQL source distribution (compatible; MySQL Enterprise & MySQL Commercial)
Protocol version:	10
Connection:		svc-9be5e8a1-8a5f-4aa7-b75d-a395570828f2-ddl.aws-oregon-1.svc.singlestore.com via TCP/IP
Server characterset:	utf8
Db     characterset:	utf8
Client characterset:	utf8
Conn.  characterset:	utf8
TCP port:		3306
Binary data as:		Hexadecimal
--------------
singlestore> show databases;
+--------------------+
| Database           |
+--------------------+
| workspace          |
| information_schema |
| memsql             |
| test               |
+--------------------+
4 rows in set (0.03 sec)

Important

The @@version and @@version_comment global variables are for compatibility with MySQL clients, which expect certain minimum version numbers and strings to be present. To check the real version of SingleStore Helios you are running, use the @@memsql_version variables instead. To check the license you are running, see the license_key and license_type status codes.

In this section

Last modified: May 17, 2024

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK