Sorry for the delay in replying back to you.
In the time since you restarted SQL Response has the problem re-appeared?
When the problem originally appeared, if known, what was the CPU usage of the SQL Response Alert Repository Service?
If the problem has re-occurred, what is the CPU usage of the SQL Response Alert Repository Service?
A support call has been created for this forum post, call reference F0035979.
Can you please attach to an e-mail the Alert Repository log file for Thursday 24th June and if the problem has re-occurred the log file for today. Please send the e-mail to firstname.lastname@example.org
and include the above call reference number in the subject field of the e-mail.