Use CData Connect Cloud to Access SingleStore Data in Microsoft Power Pivot

This article will explain how to use CData Connect Cloud to present SingleStore data as OData services and then consume the data in Microsoft Excel's Power Pivot business intelligence tool. Follow the steps below to retrieve and edit SingleStore data in Power Pivot.

Connect to SingleStore from Power Pivot

To work with SingleStore data from Power Pivot, we need to connect to SingleStore from Connect Cloud, provide user access to the connection, and create OData endpoints for the SingleStore data.

(Optional) Add a New Connect Cloud User

As needed, create Users to connect to SingleStore through Connect Cloud.

1. Navigate to the Users page and click Invite Users
2. Enter the new user's email address and click Send to invite the user
3. You can review and edit users from the Users page

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 Connect Cloud

CData Connect Cloud uses a straightforward, point-and-click interface to connect to data sources.

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 SingleStore OData Endpoints in Connect Cloud

After connecting to SingleStore, create OData Endpoints for the desired table(s).

1. Navigate to the OData page and click Add to create new OData endpoints
2. Select the SingleStore connection (e.g. SingleStore1) and click Next
3. Select the table(s) you wish to work with and click Confirm

With the connection and OData endpoints configured, you are ready to connect to SingleStore data from Power Pivot.

Import SingleStore Tables in Power Pivot

Follow the steps below to import tables that can be refreshed on demand:

1. In Excel, click Data -> Get Data -> From Other Sources -> From OData Feed
2. Fill out the OData feed URL (e.g. https://cloud.cdata.com/api/odata/service)
3. On the next screen, select Basic and configure the username and password. Password will be your PAT.

4. Select the tables that you would like to import into Excel

5. After selecting your table(s) and clicking Load, you should see the data appear in an Excel spreadsheet

6. Now, click the Power Pivot tab on the ribbon, and then select Add to Data Model. This can now work with your SingleStore data in Power Pivot.

Free Trial & More Information

If you are interested in connecting to your SingleStore data (or data from any of our other supported data sources) from Power Pivot, sign up for a free trial of CData Connect Cloud today! For more information on Connect Cloud and to see what other data sources we support, refer to our CData Connect Cloud page.