Connect with MySQL Client
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 root -h 127.0.0.1 -P 3306
Here we have -u root
to specify login as user root, -h 127.0.0.1
to connect to the SingleStoreDB host at localhost, and -P 3306
to connect to SingleStoreDB on port 3306. This is the default port setting, which can be changed if needed.
You may also use the --prompt
flag to change the prompt in the interactive session, simply to help distinguish SingleStore from MySQL:
mysql -u root -h 127.0.0.1 -P 3306 --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 14.14 Distrib 5.6.19, for osx10.9 (x86_64) using EditLine wrapper Connection id: 6 Current database: Current user: root@127.0.0.1 SSL: Not in use Current pager: stdout Using outfile: '' Using delimiter: ; Server version: 5.5.8 MemSQL source distribution (compatible; MySQL Enterprise & MySQL Commercial) Protocol version: 10 Connection: 127.0.0.1 via TCP/IP Server characterset: utf8 Db characterset: utf8 Client characterset: utf8 Conn. characterset: utf8 TCP port: 3306 --------------
singlestore> show databases; **** +--------------------+ | Database | +--------------------+ | information_schema | | memsql | | sharding | +--------------------+ 3 rows in set (0.00 sec)
singlestore> show variables like '%version%'; **** +-------------------------+------------------------------------------------------------------------------+ | Variable_name | Value | +-------------------------+------------------------------------------------------------------------------+ | memsql_version | 4.0 | | memsql_version_date | Wed May 6 09:07:03 2015 -0700 | | memsql_version_hash | 0cba132fba0ba7650c1bc9aeec8c1fc381def395 | | protocol_version | 10 | | version | 5.5.8 | | version_comment | MemSQL source distribution (compatible; MySQL Enterprise & MySQL Commercial) | | version_compile_machine | x86_64 | | version_compile_os | Linux | +-------------------------+------------------------------------------------------------------------------+ 8 rows in set (0.03 sec)
singlestore> show status like '%license%'; **** +---------------+----------------------------------+ | Variable_name | Value | +---------------+----------------------------------+ | License_key | 5ca1ab1e000f40aaa6cb67b2ea3ee466 | | License_type | enterprise | +---------------+----------------------------------+ 2 rows in set (0.00 sec)
singlestore> show status like '%cluster_capacity%'; **** +--------------------------+-------------+ | Variable_name | Value | +--------------------------+-------------+ | Maximum_cluster_capacity | 10000000 MB | | Used_cluster_capacity | 107957 MB | +--------------------------+-------------+ 2 rows in set (0.00 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 SingleStoreDB 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.