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 support@red-gate.com and include the above call reference number in the subject field of the e-mail.

Have sent the logfiles as requested - I need to do some more testing to see if the alert is behaving as expected. but obviously with this being a low disk space alert I need to be careful as and when I run the space down.

The log file you have supplied to me is from the SQL Response Client. The SQL Response Client uses .NET Remoting to connect to the Alert Repository, I can see from the log File that there where connection errors but I am unsure if they occurred when you were performing your 'Low Disk Space' Alert testing or from you restarting the SQL Response Alert Repository Service.

If you can remember at what time did you restart the Alert Repository Service.

Can you please also reply with a copy of the Alert Repository Log file for the date you performed your testing?