Why can't this stored procedure be called? (FreeTDS_JDBC and jtds)
Anton van Straaten
anton at appsolutions.com
Mon Sep 10 02:30:07 EDT 2001
The query only fails with FreeTDS. It runs in all other environments I've
tested, including other JDBC drivers (e.g. JTurbo, Sprinta), ODBC drivers,
and in SQL Server 6.5 Enterprise Manager.
I have tested that stored procedure execution is working. I have had no
problems using FreeTDS for many other procedures and
other kinds of queries. In fact, I can get the problem query to work if I
replace the "insert...execute" statement with a simple "execute", in which
case the query returns two result sets, the second one empty (which
unfortunately doesn't provide the required behavior, otherwise I would just
Changing the name "Result" to something else doesn't make a difference. In
any case, that was an artifact of the test, not the original code which
triggered the problem.
Thanks for your help, though...
> -----Original Message-----
> From: bounce-freetds-132811 at franklin.oit.unc.edu
> [mailto:bounce-freetds-132811 at franklin.oit.unc.edu]On Behalf Of
> PMoore at axa.com.au
> Sent: Sunday, September 09, 2001 9:21 PM
> To: TDS Development Group
> Subject: [freetds] Re: Why can't this stored procedure be called?
> (FreeTDS_JDBC and jtds)
> firstly i would have to ask the obvious question:
> Does it run under the SQL Server Query Analyzer tool?
> (i added it to my SQL 2000 database and apart from calling my temp table
> #tmp2 i left your code intact and verfied that your SQL works)
> i would recommend executing the sp_who procedure in your code as that is a
> known working procedure. this will at least show you whether or not stored
> procedure execution is working in your JDBC/TDS implementation.
> another thing to try - i would not use the word "Result" as the
> name of the
> column you are returning in case there is an issue with it being
> a reserved
> Peter Moore
> ITeG, Axa Australia
More information about the FreeTDS