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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...