Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →How to Work with Cvent Data in ETL Validator JDBC
Connect to Cvent from ETL Validator jobs using the CData JDBC Driver.
ETL Validator provides data movement and transformation capabilities for integrating data platforms across your organization. CData's JDBC driver seamlessly integrates with ETL Validator and extends its native connectivity to include Cvent data.
This tutorial walks through the process of building a simple ETL validator data flow to extract data from Cvent data and load it into an example data storage solution: SQL Server.
Add a new ETL Validator data source via CData
CData extends ETL Validator's data connectivity capabilities by providing the ability to add data sources that connect via CData's JDBC drivers. Connecting to Cvent data simply requires creating a new data source in ETL Validator through CData's connectiviy suite as described below.
Login to ETL Validator
Begin by logging into ETL Validator to view the application dashboard.

Click on Add a DataSource
CData extends the data source options within ETL Validator.

Click on CData
CData's connectivity is embedded within ETL Validator's data source options.

Configure the CData Driver Connection String
You will need a JDBC connection string to establish a connection to Cvent in ETL Validator.

Before you can authenticate to Cvent, you must create a workspace and an OAuth application.
Creating a Workspace
To create a workspace:
- Sign into Cvent and navigate to App Switcher (the blue button in the upper right corner of the page) >> Admin.
- In the Admin menu, navigate to Integrations >> REST API.
- A new tab launches for Developer Management. Click on Manage API Access in the new tab.
- Create a Workspace and name it. Select the scopes you would like your developers to have access to. Scopes control what data domains the developer can access.
- Choose All to allow developers to choose any scope, and any future scopes added to the REST API.
- Choose Custom to limit the scopes developers can choose for their OAuth apps to selected scopes. To access all tables exposed by the driver, you need to set the following scopes:
event/attendees:read event/attendees:write event/contacts:read event/contacts:write event/custom-fields:read event/custom-fields:write event/events:read event/events:write event/sessions:delete event/sessions:read event/sessions:write event/speakers:delete event/speakers:read event/speakers:write budget/budget-items:read budget/budget-items:write exhibitor/exhibitors:read exhibitor/exhibitors:write survey/surveys:read survey/surveys:write
Creating an OAuth Application
After you have set up a Workspace and invited them, developers can sign up and create a custom OAuth app. See the Creating a Custom OAuth Application section in the Help documentation for more information.
Connecting to Cvent
After creating an OAuth application, set the following connection properties to connect to Cvent:
- InitiateOAuth: GETANDREFRESH. Used to automatically get and refresh the OAuthAccessToken.
- OAuthClientId: The Client ID associated with the OAuth application. You can find this on the Applications page in the Cvent Developer Portal.
- OAuthClientSecret: The Client secret associated with the OAuth application. You can find this on the Applications page in the Cvent Developer Portal.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Cvent JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.cvent.jar
A typical connection string looks like this:
jdbc:cvent:OAuthClientId=MyOAuthClientId;OAuthClientSecret=MyOAuthClientSecret;InitiateOAuth=GETANDREFRESH
Licensing the Driver
To ensure the JDBC driver is licensed appropriately, copy the license file to the appropriate location:
Copy the JDBC Driver for Cvent and lic file from "C:\Program Files\CData[product_name]\lib" to
"C:\Datagaps\ETLValidator\Server\apache-tomcat\bin".
cdata.jdbc.cvent.jar
cdata.jdbc.cvent.lic
Note: If you do not copy the .lic file with the jar, you will see a licensing error that indicates you do not have a valid license installed. This is true for both the trial and full versions.
Save the connection
Should you encounter any difficulties loading the CData JDBC driver class, please contact DataGap's team, and they will provide you instructions on how to load the jar file for the relevant driver.
Add SQL Server as a Target
This example will use SQL Server as a destination for Cvent data data, but any preferred destination can be used instead.
Go to DataSources and select MS_SQL_SERVER
This option is the default.

Fill in the necessary connection details and test the connection
The details will depend on the specific target, but these details may include a URL, authentiation credentials, etc.

Create a Dataflow in ETL Validator
Open the Dataflows tab
Configured data flows will appear in this window.

Select Create Dataflow
Name your new dataflow and save it.
Open the Dataflow to view the Dataflow Diagram
The details of the data movement will be configured in this panel.

Drag & drop the JDBC as a source from the right side
Give the new source an appropriate name and save it.

Fill in the Query section of the new source
Select the Table from the Schema option that reflects which data should be pulled from Cvent data.
View the expected results of your query
The anticipated outcome of the configured query is displayed in the Result tab.

Add the destination to the Dataflow
Select Switch to Diagram, then drag & drop the DB Sink as a target from the right side (under Sink options). Give the sink an appropriate name and save it.

Set the appropriate Schema for the destination
Choose the Schema and table that matches the structure of the source table. For this example, the table on the target side was created to match the Source so that data flow seamlessly. More advanced schema transformation operations are beyond the scope of this article.

Hit the RUN option to begin replication
Running the job will take some time.

View the finished Dataflow
Return to the diagram to see the finished data replication job from Cvent data to SQL Server.

Get Started Today
Download a free, 30-day trial of the CData JDBC Driver for Cvent and start building Cvent-connected applications with ETL Validator. Reach out to our Support Team if you have any questions.