Prepared and Callable statement is always use sp_executesql

[vijayarajav]

The Microsoft SQL Server JDBC driver always uses sp_executesql internally for both PreparedStatement and CallableStatement objects. whereas dotnet SqlCommand - CommandType.StoredProcedure uses direct sql and CommandType.Text uses sp_executesql. do we have similar option in JDBC?

[machavan]

@vijayarajav you could use Statement to execute if there are not parameter bindings to do

[vijayarajav]

Thanks @machavan
Yes, but when parameter bindings are used, there’s no option to enforce direct SQL execution. We are migrating our .NET projects to Java and have observed differences in how the stored procedures are executed.

The stored procedures are vendor-specific, and we don’t have the option to modify them. Specifically, they rely on @@NESTLEVEL to return the result set to the calling procedure.