# Connecting to SingleStore

> Sisense enables easy and quick access to databases, tables, and views contained with SingleStore databases. You can import your data into a Sisense ElastiCube , or connect your data to a Sisense Live model, using Live Connect.

*Source: https://docs.sisense.com/main/SisenseLinux/connecting-to-singlestore.htm*

---

Last updated: June 10, 2026

|  |  |
| --- | --- |
| [Tier](https://www.sisense.com/pricing/#pricing) | [Deployment](https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-cloud-managed-services.md#ComparisonofManagedCloudandSelfHosted) |
| Launch     Grow    Enterprise | Cloud     On-Prem |

Sisense enables easy and quick access to databases, tables, and views contained with SingleStore databases.

You can import your data into a Sisense ElastiCube , or connect your data to a Sisense Live model, using [Introducing Live Models](https://docs.sisense.com/main/SisenseLinux/live-connect.md).

**Note:**

SingleStore (formerly MemSQL) for Linux is supported from Sisense v7.4.3.

  

[*Importing Into a Sisense ElastiCube*](#)

## Importing Data from SingleStore

**To import data from your SingleStore database:**

1. In the Data page, open an ElastiCube model or create a new ElastiCube.
2. In the Model Editor, click ![+Data](https://docs.sisense.com/main/Resources/Images/+Data.png). The Choose Connector window is displayed.

   ![ConnMgmtChooseConnector](https://docs.sisense.com/main/Resources/Images/connMgmtChooseConnector.png)
3. Choose an available [managed connection](https://docs.sisense.com/main/SisenseLinux/data-source-connection-management.md#AccessingandManagingAvailableConnections), or create a [new connection](https://docs.sisense.com/main/SisenseLinux/data-source-connection-management.md#CreatingNewConnections), for **SingleStore**. The SingleStore area is displayed.

   ![Single Store dialog](https://docs.sisense.com/main/Resources/Images/Single_Store_dialog_1190x623.png)
4. Enter the following details:
   - **Location**: Enter the computer/server IP address of the database. To connect to a
     database running on your own computer enter **localhost**.
   - In the **User Name** and **Password** fields, enter your database credentials.
   - (Optional) In **Additional Parameters**, enter additional configuration options by
     appending key-value pairs to the connection string (e.g., Timeout=60;). For a full list of connection
     string options, click [here](https://docs.memsql.com/v6.8/introduction/documentation-overview) .
5. (Optional) Select **Use SSL** if you are connecting to an SSL server. There are several options
   and requirements for connecting with SSL. See Connecting to SingleStore with SSL for more information.
6. Click ![Next](https://docs.sisense.com/main/Resources/Images/Next.png). A list of tables in
   the database are displayed. All tables and views associated with the database will appear in a new window.
7. From the Tables list, select the relevant table or view you want to work with. You can click ![8 5magnifyingglass](https://docs.sisense.com/main/Resources/Images/8-5magnifyingglass.png) next to the relevant table or view to see a preview of the data inside it.
8. (Optional) Click + to customize the data you want to import with SQL. See [Importing Data with Custom Queries](https://docs.sisense.com/main/SisenseLinux/importing-data-with-custom-queries.md) for more information.
9. After you have selected all the relevant tables, click **Done**. The tables are added to your
   schema in Sisense.

## Connecting to SingleStore with SSL

You can connect to your SingleStore database with a secure connection in Sisense. There are three options for
connecting securely:

- **SSL with no certificates** : If you connect with no certificate and your SingleStore database
  requires only a secure connection with your credentials. Select the **SSL** checkbox.
- **SSL with a Trust Certificate** : If you connect with a Trust certificate, select the
  **SSL** checkbox and enter the location of your certificate and the password. The location should
  be in the format:

  `file:C:\tmp\truststore.jks` with the prefix **file**: and the location of your .jks
  Trust certificate. If your Trust certificate is stored as a .pem file, the certificate must be converted to
  .jks. See [Converting PEM Certificates to JKS](#Converti) for more information.
- **SSL with a Client Certificate**: If you connect with a Trust and Client certificate, select the
  **SSL** checkbox and enter the location of your Trust and Client certificates and the passwords.
  The location should be in the format:

  `file:C:\tmp\keystore.jks` with the prefix **file**: and the location of your .jks
  Trust and Client certificates. If your Trust certificate is stored as a .pem file, the certificate must be
  converted to .jks. See [Converting PEM Certificates to JKS](#Converti) for more
  information.

### Converting PEM Certificates to JKS

Sisense connects to SingleStore via the Sisense Java Database Connectivity (JDBC) connector. If you connect
with SSL using a Trust or Client certificate, the files must be converted from a PEM file to a Java KeyStore
file (JKS). Java KeyStore files can be used for communication between components that are configured for SSL.

The procedure below describes how you can convert a PEM file to a JKS file with two third-party utilities,
OpenSSL and Git Bash.

**To convert a PEM file to JKS:**

1. In your Java bin directory, open Git Bash. The location of the bin directory is typically, C:\Program
   Files\Java\jdk1.8.0\_191\jre\bin where jdk1.8.0\_191 is the version of Java installed on your machine.

   ![8 5binimage](https://docs.sisense.com/main/Resources/Images/8-5binimage_717x456.png)
2. In Git Bash, enter the commands listed below that are relevant for your use case and press Enter. The bolded placeholders should be replaced by the values described below.

   **Trust Certificate**
     
   This commands convert your PEM Trust certificate file to JKS.

   `keytool -importcert -alias MySQLCACert -file **ca.pem** -keystore **truststore.jks** -storepass **mypassword**`

   **Trust and Client Certificate**

   These commands convert your PEM file to P12, and then the second command converts the P12 file to JKS.

   `openssl pkcs12 -export -in **client-cert.pem** -inkey **client-key.pem** -name "mysqlclient" -passout pass: **mypassword** -out **client-keystore.p12** keytool -importkeystore -srckeystore client-keystore.p12 -srcstoretype pkcs12 -srcstorepass **mypassword** -destkeystore **keystore.jks** -deststoretype JKS -deststorepass **mypassword**`

After running these commands, you should enter the location of certificates as the values of the
**Trust** and **Client Certificate** fields.

- **Ca.pem**: The full path of authority file (for example, C:\Users\Public\ca.pem).
- **truststore.jks**:The full path (with truststore.jks) for the new file.
- **mypassword**: The password for your certificate.
- **client-cert.pem**: The full path of your PEM certificate file (for example,
  C:\Users\Public\cert.pem).
- **client-key.pem**: The full path of your PEM private key file (for example,
  C:\Users\Public\key.pem)
- **client-keystore.p12**: The full path (with name.p12) for your new .p12 file.
- **keystore.jks**: The full path (with client.jks) for your new file path.

## Troubleshooting

### Out-of-Memory Issues

When building an ElastiCube with this connector, you might receive an "out of memory" error. To add
more memory, see [Troubleshooting Performance Issues](https://docs.sisense.com/main/SisenseLinux/troubleshooting-performance-issues.md).

[*Connecting Data to a Sisense Live Model*](#)

## Adding a SingleStore Live Connection

**To add aSingleStore live connection**:

1. In the Data page, open a Live model or create a new Live model.
2. In the Model Editor, click ![+Data](https://docs.sisense.com/main/Resources/Images/+Data.png). The Add Data dialog box is displayed.

   ![8 5JDBC1thumb](https://docs.sisense.com/main/Resources/Images/8-5JDBC1thumb030033_866x454.png)
3. Enter the following details:

   - **Location** : Enter the computer/server IP address of the database. To connect to a
     database running on your own computer enter **localhost**.
   - In the **User Name** and **Password** fields, enter your database credentials.
   - (Optional) In **Additional Parameters**, enter additional configuration options by
     appending key-value pairs to the connection string (e.g., Timeout=60;). For a full list of connection
     string options, click [here](https://docs.memsql.com/v6.8/introduction/documentation-overview).
4. (Optional) Select **Use SSL** if you are connecting to an SSL server. There are several
   options and requirements for connecting with SSL. See Connecting to SingleStore with SSL for more
   information.
5. Click ![Next](https://docs.sisense.com/main/Resources/Images/Next.png). A list of tables
   in the database are displayed. All tables and views associated with the database will appear in a new
   window.
6. From the Tables list, select the relevant table or view you want to work with. You can click ![8 5magnifyingglass](https://docs.sisense.com/main/Resources/Images/8-5magnifyingglass1.png)  
    next to the relevant
   table or view to see a preview of the data inside it.
7. (Optional) Click **+** to customize the data you want to import with SQL. See [Importing Data with Custom Queries](https://docs.sisense.com/main/SisenseLinux/importing-data-with-custom-queries.md) for more information.
8. After you have selected all the relevant tables, click **Done**. The tables are added to your
   schema in Sisense.

## Connecting to MSQL with SSL

You can connect to your SingleStore database with a secure connection in Sisense. There are three options for
connecting securely:

- **SSL with no certificates**: If you connect with no certificate and your SingleStore database requires
  only a secure connection with your credentials. Select the **SSL** checkbox.
- **SSL with a Trust Certificate**: If you connect with a Trust certificate, select the
  **SSL** checkbox and enter the location of your certificate and the password. The location should be in
  the format:

  `file:C:\tmp\truststore.jks` with the prefix **file**: and the location of your .jks Trust
  certificate. If your Trust certificate is stored as a .pem file, the certificate must be converted to .jks. See
  [Converting PEM Certificates to JKS](#Converti) for more information.
- **SSL with a Client Certificate**: If you connect with a Trust and Client certificate, select the
  **SSL** checkbox and enter the location of your Trust and Client certificates and the passwords. The
  location should be in the format:

  `file:C:\tmp\keystore.jks` with the prefix **file:** and the location of your .jks Trust and
  Client certificates. If your Trust certificate is stored as a .pem file, the certificate must be converted to .jks.
  See [Converting PEM Certificates to JKS](#Converti) for more information.

### Converting PEM Certificates to JKS

Sisense connects to SingleStore via the Sisense Java Database Connectivity (JDBC) connector. If you connect with
SSL using a Trust or Client certificate, the files must be converted from a PEM file to a Java KeyStore file (JKS).
Java KeyStore files can be used for communication between components that are configured for SSL.

The procedure below describes how you can convert a PEM file to a JKS file with two third-party utilities, OpenSSL
and Git Bash.

**To convert a PEM file to JKS**:

1. In your Java bin directory, open Git Bash. The location of the bin directory is typically, C:\Program
   Files\Java\jdk1.8.0\_191\jre\bin where jdk1.8.0\_191 is the version of Java installed on your machine.

   ![8 5binimage](https://docs.sisense.com/main/Resources/Images/8-5binimage1_701x446.png)
2. In Git Bash, enter the commands listed below that are relevant for your use case and press Enter. The bolded placeholders should be replaced by the values described below.

   **Trust Certificate**
     
   This commands convert your PEM Trust certificate file to JKS.

   `keytool -importcert -alias MySQLCACert -file **ca.pem** -keystore **truststore.jks** -storepass **mypassword**`

   **Trust and Client Certificate**

   These commands convert your PEM file to P12, and then the second command converts the P12 file to JKS.

   `openssl pkcs12 -export -in **client-cert.pem** -inkey **client-key.pem** -name "mysqlclient" -passout pass: **mypassword** -out **client-keystore.p12** keytool -importkeystore -srckeystore **client-keystore.p12** -srcstoretype pkcs12 -srcstorepass **mypassword** -destkeystore **keystore.jks** -deststoretype JKS -deststorepass **mypassword**`

After running these commands, you should enter the location of certificates as the values of the
**Trust** and **Client Certificate** fields.

- **Ca.pem**: The full path of authority file (for example, C:\Users\Public\ca.pem).
- **truststore.jks**:The full path (with truststore.jks) for the new file.
- **mypassword**: The password for your certificate.
- **client-cert.pem**: The full path of your PEM certificate file (for example,
  C:\Users\Public\cert.pem).
- **client-key.pem**: The full path of your PEM private key file (for example, C:\Users\Public\key.pem)
- **client-keystore.p12**: The full path (with name.p12) for your new .p12 file.
- **keystore.jks**: The full path (with client.jks) for your new file path.