Sign inTry Free

Transitioning Your Application

To transition your application, simply change the connection credentials to point to SingleStore.

One thing to keep in mind is Code Generation. Code generation makes loading a schema into SingleStore for the first time is slower than with MySQL. The first time SingleStore encounters a table schema, it generates and compiles code that implements infrastructure around the table (memory allocation, inserts, deletes, iterations, etc.). Once a table is compiled, SingleStore will be able to reuse it for the lifetime of your application — even if you restart the server or drop (and recreate) the table. The INSERT queries generated by mysqldump also have to be compiled exactly once.

When transitioning your application:

  • Even if you’re connecting to SingleStore locally, use the explicit host 127.0.0.1 instead of localhost. Most MySQL clients will resolve localhost to use the global MySQL socket file and ignore the port setting. See the FAQ for more information.

  • As you run through the application, monitor the memsql.log file.

  • Queries that throw errors most likely correspond to unsupported syntax (see SQL Reference for supported SQL surface area).

Last modified: November 29, 2022

Was this article helpful?

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