Hi, I hope someone out there can help.

I have a web application that uses stored procedures extensively. Up
until today, I never had a problem with returning result sets to the
browser.

However, a stored procedure I wrote today fails to return results,
even though when I run it on the server (using isql) it works fine.

The stored procedure uses temp tables, and is returning data from a
temp table.

Strangely, if a return data from a permanent table, the stored proc
returns data to the web application without any problems.

I am using sybase 11.92 on linux. There are no errors in the sybase
log, or odbc errors in the web application logs.

Any ideas as to why this is happening, and how it can be fixed, will
be gratefully received.

thanks
Raj

On Mon, 28 Jun 2004 07:09:00 -0700, Raj wrote:

Off-hand I don't see any reason why this wouldn't work. Could you post the
sproc code (or, ideally, a minimal implementation that illustrates the
problem)?

Michael
--
Michael Peppler Data Migrations, Inc.
mpeppler (AT) peppler (DOT) org http://www.peppler.org/
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or
long term contract positions - http://www.peppler.org/resume.html

Hi Raj,

No great words of wisdom but as I was reading your post I was
wondering if you had confirmed that the Web environment is calling the
SP and passing the parameters to it in EXACTLY the same way that you
do when you execute it in an isql session?? Sort of a long shot but
you never know.

Cheers,

Sara ...

r.randhawa (AT) centrio (DOT) co.uk (Raj) wrote in message news:<ba55ec3e.0406280608.4159930c (AT) posting (DOT) google.com>...

Hi, I have ever seen similar situation before, (slightly different, but
anyway),

as for my case, that is defferent behavier b/w asp stored proc and isql.

This was caused by null treatment, before starting the stored procedure,
odbc (silently) issued the command, "set ANSINULL on".
You can see this if you use audit database. If you are using asp, then
I believe same kind of things should happen to the asp.

Try to use this command from isql before using your original procedure,
and if you reproduce your original problem there, then I suspect some null
values
should be in your data, and it caused the problem.

if your permanent table data are created by isql without the above command,
this is slightly different environment, because the data itself might be
different.

Thanks

Aoki

One possibility is that it is an issue with using temp tables in
transactions.

By default, you can't create temp tables during a transaction because to do
so would put locks all over the sysobjects in tempdb and block everyone else
until you were done.

So if, perhaps before you weren't in a transaction, and now for some reason
you are, that could be your problem. What did you change? If it works OK in
isql, then perhaps it was a setting on the connection between the web server
and the database?

If it is the 'no temp table creation in a transaction' problem then you need
to somehow move the creation of the temp tables out of the transaction.

Regards,
Simon.

"Raj" <r.randhawa (AT) centrio (DOT) co.uk> wrote