Release notes

Version 3.9.0 of Splunk DB Connect was released on April 27, 2022.

New and changed features

Version 3.9.0 of Splunk DB Connect contains the following new or changed features:

Version 3.9.0 of Splunk DB Connect fixes the following issues. If no issues appear below, no issues have yet been fixed.

Date resolved	Issue number	Description
2022-03-17	DBX-5631	DBX outputs failing when data set reaches over 300K . Snowflake support is pointing to DBX limiting to 1000 records per batch

Version 3.9.0 of Splunk DB Connect contains the following known issues. If no issues appear below, no issues have yet been reported.

Date filed	Issue number	Description
2023-03-28	DBX-5771	Disable/enable connections cause "Unable to process JSON" error Workaround: In case the problem persists after migrating to a version that is supposed to be free of this bug, you will need to clear your browser caches.
2022-11-30	DBX-5790	Database account get locked after password rotation
2022-10-28	DBX-5721	Output configured in DB connect app does not work intermittently and failed to insert data in the DB when run on cron. When the output is run manually for the same data, it is successful. Workaround: When the output fails, the same is run manually and works just fine.
2022-10-19	DBX-5714	warning on startup for "Invalid key in stanza" for key "run_only_one" on Splunk 8.1.x Workaround: None needed, this option is for later splunk versions, but doesn't break anything on older ones, it's safe to ignore the warning.
2022-07-03	DBX-5666	Health Check: dbxquery command conf's filename property should be java.path, but it is: dbxquery_bridge.py now. Workaround: DB Connect works with the authentication method the customer is using. It is only the Health Check reporting the odd message which the customer flagged. The customer stated: 1. Yes, I can connect to the Microsoft SQL server using DB Connect without any issues. 2. I am using the jTDS drive with Windows Authentication.