April 21, 2008 at 12:42 pm
this weekend we had a fulldb alert run over a million times during an alter index operation because it filled up the database. nothing too much for our sql servers, but it crashed the mail server with the emails.
is there a way to limit how many times it runs? looks like it tried to run on every failure to reindex a row during the operation and it was a 300 million row table
April 21, 2008 at 1:13 pm
you can change how often the alerts are delayed but i don't think you can change the maximum time they are "alerted"
For the replication issues i set the delay to 15 minutes, then at least if its down for a couple of hours you only get 8 mails. Not gonna crash the mail server anytime soon 😛
PS, its on the options tab of the alerts
April 21, 2008 at 10:01 pm
No way to limit this. Other than perhaps have a job that counts the alerts and disables the alerts after xx firings. That would be a kludge.
This is the kind of thing MOM or System Center can do. It's why you want to carefully set alerts.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply