All Apps and Add-ons

Why does DBConnect times out with MSSQL server hostnames?

Urbanpope
Explorer

Hi all.
Hoping someone can point me in the right direction for a very annoying persistent issue.

DBX points to an MS SQL server cluster using a DNS host name in the connection string. Normally it works pretty well except for when there is a site change and a bunch of scheduled queries time out. The issue can be replicated in SQL Explorer but the timeouts can be quite inconsistent.

Tests on the search head server show that the host name is being resolved correctly and the server can connect to all resolved IPs. I did note the order of the resolved IPs is somewhat unpredictable and the IP for an offline node may be returned first.

My running theory is DBConnect is attempting to connect to the first resolved IP then failing with timeout before it's able to connect to one of the other IPs. Is this expected behaviour? Is there any way to reduce the connection timeout value?

I have found a number of posts on these boards relating to similar problems but they don't quite apply here.

Labels (3)
Tags (2)
0 Karma
Get Updates on the Splunk Community!

Splunk at Cisco Live 2025: Learning, Innovation, and a Little Bit of Mr. Brightside

Pack your bags (and maybe your dancing shoes)—Cisco Live is heading to San Diego, June 8–12, 2025, and Splunk ...

Splunk App Dev Community Updates – What’s New and What’s Next

Welcome to your go-to roundup of everything happening in the Splunk App Dev Community! Whether you're building ...

The Latest Cisco Integrations With Splunk Platform!

Join us for an exciting tech talk where we’ll explore the latest integrations in Cisco + Splunk! We’ve ...