Getting Data In

Data Lab SQL Input - Temp Table Alternatives

sochsenbein
Communicator

Hello,

I have taken on a project at work to migrate all of our old MSSQL reports into Splunk. The SQL in these reports are incredibly long - like college essay long. When I copy it directly into Data Labs input, I get this error:

com.microsoft.sqlserver.jdbc.SQLServerException: The statement did not return a result set.

I assume that this is caused by the SQL creating 4 different temp tables during its search. If this is the case, is there a simple recommended alternative? I was looking at possibly outputcsv, but think it may over complicate it with there being so many different temp tables.

Thanks

Tags (1)
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!

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...

Deep Dive: The Agentic SOC in Action with Enterprise Security Agents

Takeaways: Splunk Enterprise Security brings Agentic SOC capabilities into the analyst workflow. Agents ...