Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via sourceforge.net by Unknown author, 2 years ago
The SET SHOWPLAN statements must be the only statements in the batch. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2781) at
via jtds by michael_69
, 2 years ago
The SET SHOWPLAN statements must be the only statements in the batch. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2781) at
via sourceforge.net by Unknown author, 1 year ago
The SET SHOWPLAN statements must be the only statements in the batch. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2781) at
java.sql.SQLException: The SET SHOWPLAN statements must be
the only statements in the batch.
    at
net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365)
    at
net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2781)
    at
net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2224)
    at
net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:628)
    at
net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:525)
    at
net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:487)
    at
net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:664)
    at
net.sourceforge.jtds.jdbc.JtdsStatement.execute(JtdsStatement.java:1114)	at SQLSample.getQueryCost(SQLSample.java:4225)	at SQLSample.MSSQL_plan_statement(SQLSample.java:4160)	at SQLSample.body(SQLSample.java:480)	at com.cas.Module.exec(Module.java:1260)	at SQLSample.main(SQLSample.java:564)