Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DBADave
Constraint Violating Yak Guru
366 Posts |
 Posted - 2006-07-11 : 10:49:27
|
| What's a good way to validate if email is working on a daily basis for SQL Server 2000? I currently receive 40+ emails each day from SQL Server 2000 instances and if I receive less then that I need to determine which servers are experiencing problems. This process is manual and therefor I'm looking for an automated way to verify the status of email communications. Each month we experience email (MAPI) failures on several servers due to DC or Exchange Server reboots or other unknown issues. I don't want to convert everything to SMTP since at some point next year we will start upgrading to SQL Server 2005. Thanks, Dave |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-07-12 : 02:29:38
|
| when you send out the email,you can add the servername where it originated on the subject line?I did this kind of thingie, send myself an email every morning just to notify me that the server is up, and on other jobs some kind of email notification for status--------------------keeping it simple... |
 |
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2006-07-12 : 13:30:55
|
| Hi Jen,That's how I'm doing things today, however it's a bit of a pain when I don't receive the expected number of emails. I place a check next to the corresponding server name on a spreadsheet for each email received and then I am able to see which servers failed. I'm looking for a way to notify me only when a server is experiencing email problems.Thanks, Dave |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-07-12 : 21:01:59
|
| then you need to factor in all the possible reasons and try to catch them?in our case, for example, we only needed to know that the replication pushed through from remote site A to remote site B because of intermittent disconnections due to distance, since the replication is scheduled and we were trying to catch network disconnection we created a simple job that will send an email before and after the start of the replication and compare the number of rows between the source and destinationif you're targeting the exchange itself, better go to the heart of the problem, place a 'monitoring agent' on the exchange server, otherwise you'll realize that there are a lot of areas to cover if you go via the sql serverhope this helps...--------------------keeping it simple... |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-07-12 : 21:18:31
|
| Have each SQL Server send an email to a single SQL Server at a specified time each day. Then have that SQL Server use xp_readmail to look at all the messages to verify that it got an email from all the others. Then have that SQL Server send an email to you to let you know the results.CODO ERGO SUM |
|
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2006-07-13 : 15:42:46
|
| Hi Jen,Our Exchange Administrator does not believe this is an Exchange issue so there's not much I can do in terms of monitoring Exchange.Hi Michael,Sounds like a good plan. I could probably have the central server send its email using smtp mail to avoid the risk of MAPI failing on this particular server.Thanks, Dave |
|
|
|
|
|
|
|
|
Suggestions on How to Verify if Email is Working