Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Automated Continuous Microsoft Dataverse Replication to Apache Cassandra
Use CData Sync for automated, continuous, customizable Microsoft Dataverse replication to Apache Cassandra.
Always-on applications rely on automatic failover capabilities and real-time data access. CData Sync integrates live Microsoft Dataverse data into your Apache Cassandra instance, allowing you to consolidate all of your data into a single location for archiving, reporting, analytics, machine learning, artificial intelligence and more.
About Microsoft Dataverse Data Integration
CData provides the easiest way to access and integrate live data from Microsoft Dataverse (formerly the Common Data Service). Customers use CData connectivity to:
- Access both Dataverse Entities and Dataverse system tables to work with exactly the data they need.
- Authenticate securely with Microsoft Dataverse in a variety of ways, including Azure Active Directory, Azure Managed Service Identity credentials, and Azure Service Principal using either a client secret or a certificate.
- Use SQL stored procedures to manage Microsoft Dataverse entities - listing, creating, and removing associations between entities.
CData customers use our Dataverse connectivity solutions for a variety of reasons, whether they're looking to replicate their data into a data warehouse (alongside other data sources)or analyze live Dataverse data from their preferred data tools inside the Microsoft ecosystem (Power BI, Excel, etc.) or with external tools (Tableau, Looker, etc.).
Getting Started
Configure Cassandra as a Replication Destination
Using CData Sync, you can replicate Microsoft Dataverse data to Apache Cassandra. To add a replication destination, navigate to the Connections tab.
- Click Add Connection.
- Select Apache Cassandra as a destination.
Enter the necessary connection properties. CData Sync supports Basic authentication with login credentials and the additional authentication features of DataStax Enterprise (DSE) Cassandra. The following sections detail connection properties your authentication method may require.
You need to set AuthScheme to the value corresponding to the authenticator configured for your system. You specify the authenticator in the authenticator property in the cassandra.yaml file. This file is typically found in /etc/dse/cassandra or through the DSE Unified Authenticator on DSE Cassandra.
Basic Authentication
Basic authentication is supported through Cassandra's built-in default PasswordAuthenticator.
- Set the AuthScheme property to 'BASIC' and set the User and Password properties.
- In the cassandra.yaml file, set the authenticator property to 'PasswordAuthenticator.'
Kerberos Authentication
Kerberos authentication is supported through DataStax Enterprise Unified Authentication.
- Set the AuthScheme property to 'KERBEROS' and set the User and Password properties.
- Set the KerberosKDC, KerberosRealm, and KerberosSPN properties.
- In the cassandra.yaml file, set the authenticator property to "com.datastax.bdp.cassandra.auth.DseAuthenticator."
- Modify the authentication_options section in the dse.yaml file, specifying the default_schema and other_schemas properties as 'kerberos.'
- Modify the kerberos_options section in the dse.yaml file, specifying the keytab, service_principle, http_principle and qop properties.
LDAP Authentication
LDAP authentication is supported through DataStax Enterprise Unified Authentication.
- Set the AuthScheme property to 'LDAP' and set the User and Password properties.
- In the cassandra.yaml file, set the authenticator property to "com.datastax.bdp.cassandra.auth.DseAuthenticator."
- Modify the authentication_options section in the dse.yaml file, specifying the default_schema and other_schemas properties as 'ldap.'
- Modify the ldap_options section in the dse.yaml file, specifying the server_host, server_port, search_dn, search_password, user_search_base, and user_search_filter properties.
Using PKI
You can specify a client certificate to authenticate CData Sync with SSLClientCert, SSLClientCertType, SSLClientCertSubject, and SSLClientCertPassword.
- Click Test Connection to ensure that the connection is configured properly.
- Click Save Changes.
Configure the Microsoft Dataverse Connection
You can configure a connection to Microsoft Dataverse from the Connections tab. To add a connection to your Microsoft Dataverse account, navigate to the Connections tab.
- Click Add Connection.
- Select a source (Microsoft Dataverse).
- Configure the connection properties.
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.
- Click Connect to ensure that the connection is configured properly.
- Click Save Changes.
Configure Replication Queries
CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.
Replicate Entire Tables
To replicate an entire table, click Add Tables in the Tables section, choose the table(s) you wish to replicate, and click Add Selected Tables.
Customize Your Replication
You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication.Schedule Your Replication
In the Schedule section, you can schedule a job to run automatically, configuring the job to run after specified intervals ranging from once every 10 minutes to once every month.
Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Microsoft Dataverse data to Apache Cassandra.