All Apps and Add-ons

DB Connect 3 ignoring column order in SELECT statement

Shtark
Explorer

Since updating to DB Connect v3 columns are being returned in lexicographical order rather than the order specified in the SELECT statement.

E.g. SELECT Plan, ISP, count() now returns ISP, Plan, count(). The order per the SELECT command was correct in v2.

Anyone else experiencing this?

Fields and Table Splunk commands are obviously workarounds for now but we'd prefer not to have to select the order twice.

t183194
Explorer

Yes a fix would be great please, Im having the same issue in V3.

0 Karma

hkosuru
Explorer

Yes, I have 35 columns from the query. Cannot reorder again. Any workarounds for this?

tries
Path Finder

Only workaround idea I have is to use the table command to sort the columns (e.g. | table Plan, ISP, count(*) )

But I agree it would be great if that can get fixed and work as it used to work within v2

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!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...