|
|
Posted by Ed Murphy on 03/30/07 14:31
Zamdrist wrote:
> On Mar 30, 6:11 am, othell...@yahoo.com wrote:
>> You might consider creating a new clustered index on a column that is
>> frequently used to join with other tables. Copy paste your code to QA
>> and run a showplan with no exec, on and find out if it is doing a
>> table scan or index search.
>
> There is an index already on each of the two tables in question, one
> each on the primary key only, and it is clustered.
>
> When I run my own query with Show Execution Plan on, I see that there
> are several Clustered Index Scans, Index Scans & Parallelism/
> Repartition operations.
>
> But this is my code, running in QA. I have no control over how the
> application accesses the data.
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?
Navigation:
[Reply to this message]
|