- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello all, when creating a Stored Procedure in MSSQL and creating a new Input in Splunk DB Connect 3, I notice that if the SP contains a temporary table at all, it returns the following error:
com.micron.sqlserver.jdbc.SQLServerException: The statement did not return a result set.
Curious if anyone else has experienced this error and found a fix, and if all they needed to do was install a JDBC driver?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I figured out the problem. In order for temp tables to work in Splunk, you have to add "SET NOCOUNT ON" at the beginning of the procedure and set the Fetch Size in Splunk Web to 0 (unlimited). When creating the Data Input, it would not save, I had to write it manually through the CLI and restart the Deployer. It is now working.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I figured out the problem. In order for temp tables to work in Splunk, you have to add "SET NOCOUNT ON" at the beginning of the procedure and set the Fetch Size in Splunk Web to 0 (unlimited). When creating the Data Input, it would not save, I had to write it manually through the CLI and restart the Deployer. It is now working.
