Join the Conversation
- Find Answers
- :
- Apps & Add-ons
- :
- All Apps and Add-ons
- :
- All Apps and Add-ons
- :
- DBConnect 1 on Splunk 6.5.3
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
On a client site and they're running dbconnect 1 on 6.1 ... I know it's unsupported, but will dbconnect 1 still function on 6.5.3? We're planning on upgrading the core infra to 6.5.3 and then moving to dbconnect 3. Should dbconnect be upgraded in advance?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We're currently running DB Connect 1 on Enterprise 6.5.3. Just so you know we are seeing incredibly very different query times between DB Connect 1 and 3. For example, a SQL query ran through dbquery from DB Connect 1 will return in 9 to 12 seconds; however, when the same SQL query is ran through dbxquery from DB Connect 3 it takes 300 to 700 seconds to complete. I'm not sure why exactly but on some comments in this (https://answers.splunk.com/answers/243910/splunk-db-connect-2-is-there-a-known-search-perfor.html) I'm guessing that the health logging built into DB Connect 2 and 3 is the culprit. Hope that helps.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We're currently running DB Connect 1 on Enterprise 6.5.3. Just so you know we are seeing incredibly very different query times between DB Connect 1 and 3. For example, a SQL query ran through dbquery from DB Connect 1 will return in 9 to 12 seconds; however, when the same SQL query is ran through dbxquery from DB Connect 3 it takes 300 to 700 seconds to complete. I'm not sure why exactly but on some comments in this (https://answers.splunk.com/answers/243910/splunk-db-connect-2-is-there-a-known-search-perfor.html) I'm guessing that the health logging built into DB Connect 2 and 3 is the culprit. Hope that helps.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would have killed to have this answer last week! Still very helpful! Thank you!
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Design, Compete, Win: Submit Your Best Splunk Dashboards for a .conf26 Pass
May 2026 Splunk Expert Sessions: Security & Observability
Network to App: Observability Unlocked [May & June Series]
