Using Notebooks

SingleStore Helios supports Jupyter Notebooks for development using SQL and Python.

Import and Run Notebooks

Tip

Get Started Quickly: Notebooks in SingleStore Helios are Jupyter notebooks and if you are familiar with how to use them, you can jump right in and get started. You can access a collection of notebooks in the Gallery, where you can find how-to guides, tutorials, and getting-started information.

Import Notebooks

To access Notebooks on the Cloud Portal , select Develop > Data Studio. There are multiple ways to get started using notebooks:

  • New Notebook: Start with a new notebook (select New > New Notebook) or use a beginner notebook template such as "SingleStoreDB Notebook Basics" (recommended).

  • Import Notebook: Select New > Import From File to import a notebook from your local machine using the Import file dialog. Notebook files must be in Jupyter format (.ipynb) and the file must not exceed 5GB in size.

  • Gallery: Select the Gallery tab to find how-to guides, tutorials, and getting-started notebooks. If you are new to notebooks, SingleStore recommends using the beginner flag and taking a look at the "SingleStoreDB Notebook Basics" or "Getting Started with Notebooks" notebooks. Use labels to filter the notebooks in Gallery. To use or explore a notebook, select the notebook, and then select Try It Now. Once opened, this notebook is saved and accessible from the Recent and Personal tabs on the Data Studio page.

Run Notebooks

You can run a notebook on the Cloud Portal using any of the following methods.

Using the Notebooks UI

To run a notebook using the Notebooks UI,

  1. Open the notebook on the Cloud Portal.

  2. Select a SingleStore deployment, database, and available runtime to run the notebook.

  3. Use the available options in the Run menu to run the selected cells or all the cells in the notebook.

Using Fusion SQL Commands in a Notebook Cell

Use the RUN JOB USING NOTEBOOK Fusion SQL command in a notebook cell to run another notebook. For example:

RUN JOB USING NOTEBOOK 'example_notebook.ipynb'
WITH RUNTIME 'notebooks-cpu-small';

Refer to RUN JOB USING NOTEBOOK for more information on this Fusion SQL command.

Optionally, explore the Running Notebooks from Another Notebook with Fusion SQL notebook for an end-to-end example of running a notebook from a different notebook.

Manage Notebooks

You can perform the basic, non-development notebook tasks such as find, share, create, open/edit, delete, and rename.

Shared and Personal Tabs

Notebooks are stored in either the Shared or Personal tabs in SingleStore Helios. Notebooks stored in the Shared tab are accessible by any member of the organization.

Notebooks stored in the Personal tab are only visible to the notebook creator and cannot be shared.

Create or Open/Edit a Notebook

To create a notebook:

  1. From + New Notebook, select New Notebook.

    Steps to create a new notebook in Data Studio from +New Notebook drop-down list.
  2. Enter a name for the notebook.

  3. Select a location (Personal or Shared) for the notebook.

  4. Select a template from the template list. To create an empty notebook, select (Blank Notebook).

  5. Select Create.

A dialog box for creating a notebook.

To open (or edit) an existing notebook, select the notebook in the list of notebooks.

Save a Notebook

Notebooks are automatically saved (autosave) every 5 seconds.

Session Limits

Each user can start one notebook session at a time. The session limits for Notebooks are:

  • Idle timeout: 15 mins

  • Long code execution timeout: 1 hour

  • Session age timeout: 8 hours

Once the timeouts reach their limit, the system automatically terminates the notebook session and deletes any unsaved data (state/variables/files).

Share a Notebook

All users within the same organization have access to the notebooks that are located in the Shared tab.

To share a notebook that is in the Shared tab, select Copy Link from the (three-dot) under the Actions column for your notebook. Share the link with other users in the same organization.

Share a notebook in Data Studio using Share option under Actions column.

To share a notebook that is in the Personal tab, duplicate the notebook and change the location to a Shared tab.

Rename a Notebook

To rename a notebook, select Rename from the (three-dot) under the Actions column for your notebook

Duplicate a Notebook

To duplicate a notebook, select Duplicate from the (three-dot) under the Actions column for your notebook.

Enter a name for the notebook and select a location. If you duplicate a notebook from the Personal tab to a Shared tab, the new notebook will not be private.

Delete a Notebook

To delete a notebook, select Delete from the (three-dot) under the Actions column for your notebook

Last modified: April 23, 2025

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