ServiceNow connector overview
The ServiceNow connector is in gated Public Preview. To participate in the preview, contact your Databricks account team.
The ServiceNow connector allows you to ingest data from ServiceNow into Databricks.
How does the connector pull data from ServiceNow?
The ServiceNow connector uses the ServiceNow Table API v2.
Could using the Table API impact the ServiceNow instance?
Yes. However, the impact depends on the amount of data ingested. For example, it is typically more noticeable in the initial snapshot than during an incremental read.
Why is my ServiceNow ingestion performance slow?
Databricks recommends working with your ServiceNow administrator to enable ServiceNow-side indexing on the sys_updated_on field. This is a standard approach for improving performance when ingesting using the ServiceNow APIs. Setting the index allows Databricks to avoid fully scanning the entire sys_updated_on column, which can bottleneck large updates. For instructions, see Create a table index in the ServiceNow documentation. If the issue persists, create a support ticket.
SCD type 1 vs. type 2
The Slowly Changing Dimensions (SCD) setting determines how to handle changes in your data over time. Enable SCD type 1 (history tracking off) to overwrite outdated records as they're updated and deleted in the source. Enable SCD type 2 (history tracking on) to maintain a history of those changes. Note that deleting a table or column does not delete that data from the destination, even when SCD type 1 is selected.