April 16, 2009 at 2:10 pm
how about an hard IIS reset or "recycle" of application pools .... can that be causing the issue ?
See the IIS logs.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
April 16, 2009 at 2:16 pm
jacek0 is right. application that uses global temp table is not the same application that exec sp_reset_connection. And they arenot using same databases since they are two different application. Moss is the application that exec sp_reset_connection on temp database.
April 16, 2009 at 2:19 pm
IIS reset??? Does all the application will have IIS set. I know MOSS has IIS but don't know about the other application have IIS setup that is using this global temp table and creating problem.
April 16, 2009 at 2:39 pm
ruchika thapa (4/16/2009)
jacek0 is right. application that uses global temp table is not the same application that exec sp_reset_connection. And they arenot using same databases since they are two different application. Moss is the application that exec sp_reset_connection on temp database.
MOSS cannot drop any temp tables of another application using another DB because that stored procedure uses the context as I explained it. If MOSS is not using code to shrink tempdb it will not drop a temp table in another database.
http://www.sqldev.net/misc/sp_reset_connection.htm
Security context, which is why connection pooling matches connections based on the exact connection string
The exact connection includes catalog which is database name only reset or Shrink operation can drop items belonging to another database.
Kind regards,
Gift Peddie
April 16, 2009 at 3:56 pm
I think the vendor needs to explain why they are using global temp tables; do they really understand how they work under the covers? I'm not sure how they can claim it's a server issue unless they can show that their code is holding the reference open somehow.
Viewing 5 posts - 31 through 34 (of 34 total)
You must be logged in to reply to this topic. Login to reply