Generally speaking, getting a spike above 60% is nothing to worry about. How
long does the processor stay above 60%? If it is for several seconds, then
you might have something to think about.
First, how is your table indexed? I would hope as a minimum you have an
index on the Fault_No and
- Stacy Mader [EMAIL PROTECTED] on 07/29/01 23:03:10 +1000:
With our report/response database, fault_no's can have one, multiple or
null response_no's. The SQL below returns distinct fault_no's regardless
if it has one, multiple or null response's. The SQL does the job, but
can you figure
Steve,
Thanks for the info. The view was created using the fault_no column as the common
link between my two original tables.
Using your idea of the GROUP BY clause, I created another view
(report_response_index)
which contains only the fault_no and latest response_no. Created like:
CREATE
