October 11, 2004 at 11:58 pm
hi,
i don't this is the right place to post this message. Whatever, i need help from here.
i've a VB application on SQl 200 server which has been run for 10 month. But recently, one of the procedure ran over 1.5 days which is 20 miniutes in the past. so i trace it with the Profiler and find that there are many many locks and release process in SQL but nothing to do with the query. i find that there are 2 tables is lock by my process but i don't know what to do next. Do i need to set the lock timeout on the SQL server or anything else? Please advice on me. Urgent help!
Best Regards,
Jeff
October 12, 2004 at 10:33 am
What does the process do? Perhaps the data has changed. Be sure you run update statistics on the tables involved, also check dbcc showcontig for fragmentation. If it's drastically changed, something must be different.
October 13, 2004 at 6:34 am
Also consider that an index may have been altered, added, or deleted deliberately or accidentally. Also, statistics could have been updated and actually backfired causing SQL Server to guess poorly on the execution plan (not at all likely, but I suppose it could happen). The latter is moor likely with poorly coded SQL. Also, even a small and supposedly innocent change to the SQL could have had a major impact on SQL Servers ability to generate a good execution plan. The last idea is that some other SPID might have been blocking it. If it hangs again try sp_who2 and other means to identify a blocking situation. If none of the above remind you of what might be causing the problem try looking at the execution plan within Query Analyzer.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply