March 14, 2007 at 8:18 pm
I have a user db with several stored procedures, but one stored procedure sometimes shows as running from master db context. Why? The proc doesn't even exist there. How does SQL 2005 handle this?
Secondly our tempdb grew to a large size and we noticed that the performance of the queries which rely on temp tables is very slow. Usually they run for few seconds, but with tempdb full they run for about 2 min. The problem goes away once SQL instance is restarted and tempdb goes back to it's original size.
BTW, no, the temp db does not grow while the queries are running, so it's not slow because it's trying to expand the tempdb.mdf
March 15, 2007 at 4:22 am
I dont think tempdb usage has anythign to do with your procedure context question.
I am aware of an issue with SQL 2005 tempdb and temporary tables cleanup. The fix is available at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;933097
check if you can apply that.
March 15, 2007 at 9:31 am
Thanks, I'll research the fix further. Maybe it is an answer to my problems.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply