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!

Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA

Join us on Wed, Dec 10. at 10AM PST / 1PM EST for a live webinar and demo with Splunk experts! Discover how ...

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...