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
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...