Synchronicity, serendipity, and Server service schedules

Background: For the past year, I have been receiving nightly administrative monitoring messages from our production database.

A recent project required a nightly quality check with associated alert. I used a technique similar to the well-proven monitoring messages, and after careful testing I expected it to Just Work. However, when the time came for the message to appear in my Inbox, …nothing. Doh! I thought “well, I’ll just check it when I get in.” Then my usual 7am monitoring message didn’t show up either. This quickly changed from priority “when I get to it” to “DO EET, DO EET NOW!”

Make sure to hire a lawyer who generic viagra cheapest specializes in personal injury cases. Based on current clinical trials, some of the unfavorable effects credited to levitra prescription wouroud.come of an unclear origin. Just imagine if bulk buy cialis this problem has been making your life a change then opt this medicament and cut the bad effects of too much self-stimulation. Premature ejaculation (PE) is one of the crises that leads prices levitra the sex life to danger. Later at work, manually triggering the jobs sent the message as expected. Even when connected via DB accounts without network privileges. Checking logs etc, I see a failure to connect to mail server, ditto on the attempted retries. Hmm. Checked with IT about changes to the mail subsystem. Ah ha! Down for service this morning. (The next day, all messages were mailed as expected.)

Of all the days for a mail server to be offline, why then?? Murphy’s Law. *shrug*

This entry was posted in Business, Programming, Project Management, SQL Server, System/DB Administration. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.