|
|
Posted by Zamdrist on 03/30/07 14:51
On Mar 30, 8:31 am, Ed Murphy <emurph...@socal.rr.com> wrote:
>
> If your query is the same as what the application runs, except for
> specific values being plugged in here and there, then the application
> will generally get the same execution plan that you do.
>
> Does QA run your query reasonably quickly? Based on the Profiler
> trace, does the application seem slow because it runs slow queries,
> or because it runs an inefficiently large number of queries which
> are reasonably fast individually?
Here is the query I ran, it returns 70.8K rows in 2 seconds via QA:
Select M.MatterID From Matters M
Inner Join MatterConflicts MC On MC.Matters = M.Matters
Inner Join Matters M2 On M2.Matters = MC.HitMatters
Inner Join MatterConflictHits MCH On MCH.MatterConflicts =
MC.MatterConflicts
Now the application is doing all kinds of things, probably more
complicated than my query above. Honestly I don't know enough about
Profiler to isolate one operation. I did check it out and there are
many, many sp_cursorexecute, prepare and close statements, along with
many select fields from tables queries.
I dunno, I doubt I will be able to make any sort of significant impact
on performance without access to the code.
FYI: This program is a legal case management software called Prolaw by
Thomson-Elite...it *sucks* royally! LOL.
Navigation:
[Reply to this message]
|