All Apps and Add-ons

Splunk DB Connect 2: Compatibility with MS SQL JDBC 4.2

cjj1977
Path Finder

In the documentation for Splunk DB Connect v2.4.0, the only MS SQL JDBC driver mentioned seems to be the older 4.0 version: sqljdbc4.jar. In the documentation for Splunk DB Connect v3.1.0 the recommended MS SQL JDBC driver is version 4.2: sqljdbc42.jar.

http://docs.splunk.com/Documentation/DBX/2.4.0/DeployDBX/Supporteddatabases
http://docs.splunk.com/Documentation/DBX/3.1.0/DeployDBX/Installdatabasedrivers

Does anyone know if the more recent JDBC 4.2 driver works correctly with DB Connect 2.4.0?

I also notice that Microsoft don't seem to support JDBC 4.0 with JRE 1.8:
https://docs.microsoft.com/en-us/sql/connect/jdbc/system-requirements-for-the-jdbc-driver


Motivation: The migration process from 2.4.0 to 3.1.0 simply keeps the same driver, moving it to a new location it seems. This is understandable. I'd like to upgrade the JDBC drivers first, maybe X weeks before migrating the whole app so I don't have to include that in the migration (or back-track if something goes wrong).

0 Karma

cjj1977
Path Finder

In case anyone is wondering, I have been running DB Connect v2.4.0 with JDBC 4.2 on JRE 1.8 for a few weeks now without any problem. I guess that proves that it is compatible, at least well enough for me...

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...