Ready to get started?

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

Free Trial

Connect to Microsoft Dataverse Data as a SQL Server Linked Server



Use CData Connect Cloud to create a linked server for live Microsoft Dataverse 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 Microsoft Dataverse data from your SQL Server database. This article demonstrates how to connect to Microsoft Dataverse using Connect Cloud and query Microsoft Dataverse data in SQL Server Management Studio (SSMS).

CData Connect Cloud provides a pure SQL Server interface for Microsoft Dataverse, allowing you to query data from Microsoft Dataverse 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 Microsoft Dataverse, leveraging server-side processing to return the requested Microsoft Dataverse data quickly.

Configure Microsoft Dataverse Connectivity for SQL Server

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

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

    You can connect without setting any connection properties for your user credentials. Below are the minimum connection properties required to connect.

    • InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
    • OrganizationUrl: Set this to the organization URL you are connecting to, such as https://myorganization.crm.dynamics.com.
    • Tenant (optional): Set this if you wish to authenticate to a different tenant than your default. This is required to work with an organization not on your default Tenant.

    When you connect the Common Data Service OAuth endpoint opens in your default browser. Log in and grant permissions. The OAuth process completes automatically.

  4. Click Create & Test
  5. Navigate to the Permissions tab in the Add Microsoft Dataverse 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 Microsoft Dataverse 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, CDS1).
  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, [email protected].
    • 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 Microsoft Dataverse linked server from any tool that can connect to SQL Server. An example SQL query would be: SELECT * FROM [CDATA CONNECT CLOUD].[CDS1].[CDS].[Accounts] We have successfully created a linked server that allows us to query Microsoft Dataverse 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!