> I expect that for some reason the transaction that is inserting into #temp is running in ISO 3 - perhaps to
> make sure the select portion is consistent. I would check to see if that is really necessary as a first step.
We don't ever use isolation level 3 - at least we don't explicitly.
> the connection is in a connection pool and someone didn't clean up after an iso3 query
Why don't the drivers automatically do this after using the connection.
I'm guessing the problem is with the connection pool and some other proc implicitly having a isolation level of 3. We've had numerous problems with connection pool been left in a bad state.
MS-SQL handles this really well - connection is reset after its returned to the pool - why can't SAP do the same thing. I know the SAP/Sybase hasn't invested very much in .net; is this likely to improve in the future ?
> One other possibility is that the coder might have done something like:
> if exists (select * from sysobjects where name like '#monoFun%')
> insert into #monoFun select * from ...
I've checked this and there's no checking of sysobjects in this proc.
Thanks