July 16, 2009 at 6:00 am
Hi Everyone,
I have a code which is a simple select that joins with 2 other tables within a stored procedure (doesnt take any parameters), what I noticed was that if the proc is called within QA, it returns results within milliseconds, but we have the sp within a VB application to present data, I can see that procedure starting on profiler trace, but it never completes and eventually time out.
No locks are being held within the database, but yet it returns no results when called within the application, the fix here was to restart the SQL service.
Is there an explanation for such behaviour ?
July 16, 2009 at 6:09 am
At a guess, it could be something to do with session settings, ie SET ANSI_NULLS , SET CONCAT_NULL_YIELDS NULL etc...
Confirm that they are the same in sys.dm_exec_sessions
July 16, 2009 at 7:34 am
its a sql 2k database, so no sys schema
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply