Thank you very much for your quick reply , this answer never even dawned on me

Thomas H wrote:

>Note: If view is to be used in "read-only" situations, using >WITH NOLOCK hints may help in the area of "locking".

This will prevent locking on the tables right?

I've found that if I use WITH(NOLOCK), my Selects return that much faster... SQL BOL states

READUNCOMMITTED

Specifies that dirty reads are allowed. This means that no shared locks are issued and...

This seems to have a longer run time than the previous ones, I keep yielding an even 8 seconds or 8000ms average run time as compared to even any of...

1) ah, ok, I thought there was a setting in QA to change the output time display.

2) fair enough... Is my table just...

Thanks again Jonathan for your help,

2 quick questions ...

1) how do I measure in milliseconds, till now i've been getting the time displayed in the status bar in...

Jonothan,

Thanks for your post, and yes, the query plan for the 1st and 3rd query were the same, it's kinda bizzar that the 3rd is still even a...

I modified the where clause to show the having, which I missed and posted way to early to this forumn, but maybe there is something that can be done? :S

--RUNTIME:18

--(80411...

I forgot to mention that the 81898 results are ALL the records in that table, why would the EXISTS not filter out any data?

Thanks,