|
| I know how to fix the issue if it comes up again, but don't understand why
it happens or whether it is a bug or by design.
There is a simple VB COM+ component with a method that calls a stored
procedure. The component does not support transactions or have state. There
is no any logic inside the method at all - just a stored procedure call. The
component is used very heavily and average call time in COM+ MMC is around
10ms.
Now, all of the sudden (of course things like that happen on Friday at 5pm)
the users start complaining that the app response time is terrible. I look
into COM+ MMC and see that the call time for the component went up to 15 -
20 seconds. Sometimes it was even more than 30 sec, so the app was timing
out.
I opened up Query Analyzer on the server where the component resides under
the same user that the component runs under and executed the stored
procedure from the method with the same parameter - comes back immediately.
However, the same stored procedure with everything else the same runs 20
seconds if called from COM+ component.
After we opened and recompiled the stored procedure the issue went away, at
least for now.
I don't understand why it happens. How calling a stored procedure from Query
Analyzer differ calling it from COM+ component? Is it a bug? Has anybody
seen this before?
Thanks,
-Stan
|
|