Process & Analyze Veeva Data in Azure Databricks

Databricks is a cloud-based service that provides data processing capabilities through Apache Spark. When paired with the CData JDBC Driver, customers can use Databricks to perform data engineering and data science on live Veeva data. This article walks through hosting the CData JDBC Driver in Azure, as well as connecting to and processing live Veeva data in Databricks.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live Veeva data. When you issue complex SQL queries to Veeva, the driver pushes supported SQL operations, like filters and aggregations, directly to Veeva and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying allows you to work with and analyze Veeva data using native data types.

Install the CData JDBC Driver in Azure

To work with live Veeva data in Databricks, install the driver on your Azure cluster.

1. Navigate to your Databricks administration screen and select the target cluster.
2. On the Libraries tab, click "Install New."
3. Select "Upload" as the Library Source and "Jar" as the Library Type.
4. Upload the JDBC JAR file (cdata.jdbc.veevavault.jar) from the installation location (typically C:\Program Files\CData[product_name]\lib).

Connect to Veeva from Databricks

With the JAR file installed, we are ready to work with live Veeva data in Databricks. Start by creating a new notebook in your workspace. Name the notebook, select Python as the language (though Scala is available as well), and choose the cluster where you installed the JDBC driver. When the notebook launches, we can configure the connection, query Veeva, and create a basic report.

Configure the Connection to Veeva

Connect to Veeva by referencing the class for the JDBC Driver and constructing a connection string to use in the JDBC URL. Additionally, you will need to set the RTK property in the JDBC URL (unless you are using a Beta driver). You can view the licensing file included in the installation for information on how to set this property.

driver = "cdata.jdbc.veevavault.VeevaVaultDriver"
url = "jdbc:veevavault:RTK=5246...;User=myuser;Password=mypassword;Server=localhost;Database=mydatabase;"

Built-in Connection String Designer

For assistance in constructing the JDBC URL, use the connection string designer built into the Veeva JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

Fill in the connection properties and copy the connection string to the clipboard.

You are ready to connect after specifying the following connection properties:

• Url: The host you see in the URL after you login to your account. For example: https://my-veeva-domain.veevavault.com
• User: The username you use to login to your account.
• Password: The password you use to login to your account.

Load Veeva Data

Once the connection is configured, you can load Veeva data as a dataframe using the CData JDBC Driver and the connection information.

remote_table = spark.read.format ( "jdbc" ) \
	.option ( "driver" , driver) \
	.option ( "url" , url) \
	.option ( "dbtable" , "NorthwindProducts") \
	.load ()

Display Veeva Data

Check the loaded Veeva data by calling the display function.

display (remote_table.select ("ProductId"))

Analyze Veeva Data in Azure Databricks

If you want to process data with Databricks SparkSQL, register the loaded data as a Temp View.

remote_table.createOrReplaceTempView ( "SAMPLE_VIEW" )

The SparkSQL below retrieves the Veeva data for analysis.

% sql

SELECT ProductId, ProductName FROM NorthwindProducts WHERE CategoryId = 5

The data from Veeva is only available in the target notebook. If you want to use it with other users, save it as a table.

remote_table.write.format ( "parquet" ) .saveAsTable ( "SAMPLE_TABLE" )

Download a free, 30-day trial of the CData JDBC Driver for Veeva and start working with your live Veeva data in Azure Databricks. Reach out to our Support Team if you have any questions.