Ready to get started?

Learn more about CData Connect Cloud or sign up for free trial access:

Free Trial

Connect to SingleStore Data as a SQL Server Linked Server



Use CData Connect Cloud to create a linked server for live SingleStore data.

SQL Server Linked Servers enable the SQL Server Database Engine to read data from remote data sources and execute commands against the remote database servers outside of the instance of SQL Server. Typically, linked servers are configured to enable the execution of a T-SQL statement that includes tables in another instance of SQL Server, or another database product such as Oracle. When paired with CData Connect Cloud, linked servers provides instant access to SingleStore data from your SQL Server database. This article demonstrates how to connect to SingleStore using Connect Cloud and query SingleStore data in SQL Server Management Studio (SSMS).

CData Connect Cloud provides a pure SQL Server interface for SingleStore, allowing you to query data from SingleStore without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect Cloud pushes all supported SQL operations (filters, JOINs, etc.) directly to SingleStore, leveraging server-side processing to return the requested SingleStore data quickly.

Configure SingleStore Connectivity for SQL Server

Connectivity to SingleStore from SQL Linked Servers is made possible through CData Connect Cloud. To work with SingleStore data from SQL Linked Servers, we start by creating and configuring a SingleStore connection.

  1. Log into Connect Cloud, click Connections and click Add Connection
  2. Select "SingleStore" from the Add Connection panel
  3. Enter the necessary authentication properties to connect to SingleStore.

    The following connection properties are required in order to connect to data.

    • Server: The host name or IP of the server hosting the SingleStore database.
    • Port: The port of the server hosting the SingleStore database.
    • Database (Optional): The default database to connect to when connecting to the SingleStore Server. If this is not set, tables from all databases will be returned.

    Connect Using Standard Authentication

    To authenticate using standard authentication, set the following:

    • User: The user which will be used to authenticate with the SingleStore server.
    • Password: The password which will be used to authenticate with the SingleStore server.

    Connect Using Integrated Security

    As an alternative to providing the standard username and password, you can set IntegratedSecurity to True to authenticate trusted users to the server via Windows Authentication.

    Connect Using SSL Authentication

    You can leverage SSL authentication to connect to SingleStore data via a secure session. Configure the following connection properties to connect to data:

    • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
    • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
    • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
    • SSLClientCertType: The certificate type of the client store.
    • SSLServerCert: The certificate to be accepted from the server.

    Connect Using SSH Authentication

    Using SSH, you can securely login to a remote machine. To access SingleStore data via SSH, configure the following connection properties:

    • SSHClientCert: Set this to the name of the certificate store for the client certificate.
    • SSHClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
    • SSHClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
    • SSHClientCertType: The certificate type of the client store.
    • SSHPassword: The password that you use to authenticate with the SSH server.
    • SSHPort: The port used for SSH operations.
    • SSHServer: The SSH authentication server you are trying to authenticate against.
    • SSHServerFingerPrint: The SSH Server fingerprint used for verification of the host you are connecting to.
    • SSHUser: Set this to the username that you use to authenticate with the SSH server.
  4. Click Create & Test
  5. Navigate to the Permissions tab in the Add SingleStore Connection page and update the User-based permissions.

Add a Personal Access Token

If you are connecting from a service, application, platform, or framework that does not support OAuth authentication, you can create a Personal Access Token (PAT) to use for authentication. Best practices would dictate that you create a separate PAT for each service, to maintain granularity of access.

  1. Click on your username at the top right of the Connect Cloud app and click User Profile.
  2. On the User Profile page, scroll down to the Personal Access Tokens section and click Create PAT.
  3. Give your PAT a name and click Create.
  4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

Connect to SingleStore from SQL Server using Connect Cloud

To establish a connection from SQL Server Linked Server to the CData Connect Cloud Virtual SQL Server API, follow these steps.

  1. Open Microsoft SQL Server Management Studio.
  2. In the Object Explorer pane, open Server Objects, right-click Linked Servers, and select New Linked Server.
  3. The New Linked Server dialogue opens. On the General page, enter the following information:
    • Enter a name for the server in the Linked server field.
    • Select the radio button Other data source and select SQL Server Native Client 11.0 as the provider.
    • In the Data source field, enter tds.cdata.com,14333
    • In the Catalog field, enter enter the Connection Name of the CData Connect Cloud data source you want to connect to (for example, SingleStore1).
  4. Select the Security page. At the bottom, select the radio button labeled Be made using this security context and enter the following information:
    • Remote login - enter your CData Connect Cloud username. This is displayed in the top-right corner of the CData Connect Cloud interface. For example, test@cdata.com.
    • With password - enter the PAT you generated on the Settings page.
  5. Click OK to create the server.
  6. Your linked server can now be used to access the data in the data source you specified. If you need to access data from more sources, create another linked server for each one.

Execute Queries

You can now execute queries to the SingleStore linked server from any tool that can connect to SQL Server. An example SQL query would be: SELECT * FROM [CDATA CONNECT CLOUD].[SingleStore1].[SingleStore].[Orders] We have successfully created a linked server that allows us to query SingleStore data.

Get CData Connect Cloud

To get live data access to 100+ SaaS, Big Data, and NoSQL sources directly from your SQL Server database, try CData Connect Cloud today!