Data Engineering · Topic 8 of 16

ServiceNow and Google Analytics Connectors, JDBC and ODBC Drivers

Learn the Snowflake Connectors for ServiceNow and Google Analytics, and when to use the JDBC and ODBC drivers, with connection basics and network needs.

  • 4 min
In a nutshell
  • ServiceNow connector: Native App, table API v2, tables with sys_id, initial then incremental load, warehouse with auto resume.
  • Google Analytics connector: Raw Data (BigQuery export, event level) and Aggregated Data (reporting API); GA4 only.
  • JDBC for Java; ODBC for native and BI clients; both use HTTPS and support PUT and GET.

What it is

Two kinds of tools sit here. The Snowflake Connectors for ServiceNow and Google Analytics are packaged applications that pull data from a SaaS source into your account with no code. Drivers (JDBC and ODBC) are the standard database interfaces that applications, BI tools and programs use to run SQL against Snowflake.

The first answers "how do I ingest this SaaS data with the least work?" The second answers "how does this tool or language talk to Snowflake?"

ServiceNowREST table APIconnector appSnowflake tablesinitial load, then incrementalGA4 dataBigQuery exportconnector appSnowflake tablesBI tool or Java appJDBC or ODBCSnowflakeSQL over HTTPS

How it works

Snowflake Connector for ServiceNow

The connector is a Snowflake Native App, installed from the Snowflake Marketplace, that ingests ServiceNow data into your account. It uses version 2 of the ServiceNow table API and can ingest only tables that have a sys_id column. It covers data such as incidents, changes, users, service catalog items, configuration items and assets.

It does an initial load of historical data and then pulls incremental changes on a schedule you control. A virtual warehouse with auto resume runs the work; serverless compute is not supported.

Limits worth knowing: views and archived records are not ingested, and instances restricted by IP address or behind a VPN are not supported. A schema change in ServiceNow does not update rows already ingested unless those rows change again. Destination schemas with managed access are not supported.

Snowflake Connector for Google Analytics

This family of Native Apps loads Google Analytics 4 data. There are two variants.

VariantDataSource
Raw DataEvent level GA4 dataRead from the BigQuery export that you link to the GA4 property, using the BigQuery Storage API
Aggregated DataAggregated report dataPulled through the Google Analytics reporting API

Only GA4 properties are supported, not Universal Analytics. The tables and views in the destination schema belong to the connector while it is installed, so build your own models in another schema. For the raw variant, the GA4 property must first be linked to a Google Cloud project so raw data is exported to BigQuery.

Exam tip

Both connectors install as Native Apps and share a pattern: install, configure the source connection, choose what to ingest, set a schedule. If an answer needs custom code or a tool outside Snowflake for these two sources, a connector is the better choice.

Drivers

Snowflake drivers connect applications to Snowflake. All of them send SQL over HTTPS (port 443) and receive results that can be downloaded in chunks directly from cloud storage.

DriverLanguage and useConnection basics
JDBCJava applications and Java based BI tools (a Type 4 driver, so pure Java)URL jdbc:snowflake://<account>.snowflakecomputing.com/ plus properties
ODBCC and C++ applications and BI tools such as Excel or TableauPlatform driver, configured through a DSN or a connection string
OthersPython, Go, .NET, Node.js, PHP PDO, CEach has its own package

Both JDBC and ODBC support the full SQL set, including PUT and GET for staging files. Authentication options include password, key pair, OAuth and SSO through an external browser. JDBC properties such as warehouse, db, schema and role set the session context.

ApplicationJavaJDBC driverHTTPS 443SQLSnowflakeExcel or BI toolODBC DSNHTTPS 443SQLSnowflake

Because result chunks come from cloud storage, a firewall that allows only the Snowflake hostnames can still break large result sets. The next page shows how SYSTEM$ALLOWLIST lists every host the drivers need.

Common mistakes

Assuming the ServiceNow connector reaches any instance. Instances behind IP restrictions or a VPN are not supported.

Using serverless compute for the ServiceNow connector. It needs a warehouse with auto resume.

Building tables inside the connector's destination schema. The connector owns that schema; use a separate one.

Picking ODBC for a Java service. A Java application uses JDBC; ODBC is for native and BI clients.

Opening only the Snowflake account host in a firewall. Large results and stage access use cloud storage hosts, which must be allowed too.

What to remember for the exam

  • ServiceNow connector: Native App, table API v2, tables with sys_id, initial then incremental load, warehouse with auto resume.
  • Google Analytics connector: Raw Data (BigQuery export, event level) and Aggregated Data (reporting API); GA4 only.
  • JDBC for Java; ODBC for native and BI clients; both use HTTPS and support PUT and GET.
  • Drivers need the account host and cloud storage hosts reachable.
  • Use a ready made connector before building custom ingestion for a supported SaaS source.

Check yourself

  • What must a ServiceNow table have to be ingested by the connector?

    A sys_id column, because the connector uses the ServiceNow table API and needs that key.

  • Which Google Analytics connector variant gives event level data?

    The Raw Data variant, which reads the GA4 BigQuery export.

  • Which driver would a Java service use to query Snowflake?

    The JDBC driver, with a jdbc:snowflake:// URL.

Topic 8 of 16 in Data Engineering

Test yourself on Data Engineering

The full Snowflake ARA-C01 question bank has 687 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.