The CData JDBC Driver for Veeva Vault models Veeva Vault objects as relational views. A Veeva Vault object has relationships to other objects; in the views, these relationships are expressed through foreign keys. The following sections show the static endpoints of the Veeva Vault API.

However, the rest of the views are dynamically determined, using the metadata exposed on the Veeva Vault API. All vault objects will be exposed by the CData JDBC Driver for Veeva Vault. However, we only only list views in the help for types we can determine at design time all available columns. Examples of Veeva objects availabe with the CData JDBC Driver for Veeva Vault but not displayed in the help include:

• Documents (Query the available documents, VQL is used when possible for this object.)
• Users (Query the exisiting users, VQL is used when possible for this object.)
• Groups (Query the exisiting groups, VQL is used when possible for this object.)
• {Every Vault Object} (Query any vault object on its own view. VQL is always used to query Vault Object's views.)

About Veeva Vault Query

Veeva Vault Query (VQL) is a query language similar to SQL. It is available to use via the Veeva Vault API. When the query can be handled server-side, the provider transforms SQL to VQL and sends it to Veeva Vault. Optimizing in this way decreases the execution time, since the filtering will be done server-side.

Also, the provider supports QueryPassthrough, which means that you can write a VQL query and directly send it to Veeva Vault. This can be done by setting QueryPassthrough connection property to true.