https://community.splunk.com/t5/Getting-Data-In/Data-Lab-SQL-Input-Temp-Table-Alternatives/m-p/434272#M100258 <P>Hello,</P> <P>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:</P> <P>com.microsoft.sqlserver.jdbc.SQLServerException: The statement did not return a result set.</P> <P>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.</P> <P>Thanks</P> Tue, 10 Jul 2018 16:47:55 GMT sochsenbein 2018-07-10T16:47:55Z https://community.splunk.com/t5/Getting-Data-In/Data-Lab-SQL-Input-Temp-Table-Alternatives/m-p/434272#M100258 <P>Hello,</P> <P>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:</P> <P>com.microsoft.sqlserver.jdbc.SQLServerException: The statement did not return a result set.</P> <P>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.</P> <P>Thanks</P> Tue, 10 Jul 2018 16:47:55 GMT https://community.splunk.com/t5/Getting-Data-In/Data-Lab-SQL-Input-Temp-Table-Alternatives/m-p/434272#M100258 sochsenbein 2018-07-10T16:47:55Z