ending email from SQL Server can be a useful way to keep yourself or the system's administrator informed of any errors and alerts, but depending on your version of SQL Server, the setup can be quite involved or relatively simple. With SQL Server 2000, the setup requires a heavy email client, such as Microsoft Outlook, or a rather convoluted stored procedure. SQL Server 2005 vastly improved the process by adding email functionality to Management Studio
. (The feature remains in SQL Server 2008.)
This article explains the processes for sending email from SQL Server 2000 and from SQL Server 2005/2008.
Send Email from SQL Server 2000
To send email from SQL Server 2000, you can use Outlook (or another email client) or Blat
, a command-line executable SMTP email client that allows you to forego Outlook and a POP3 account (if you're not using Exchange). Blat
is flexible enough to handle attached reports and formatting, and it's free.
To use the Blat option, you would wrap the call to the command line in a function or stored procedure. For instance, you could use the following statement to call the stored procedure in Listing 1:
Exec stp_BlatMail 'ServerName', 'firstname.lastname@example.org',
'System Maintenance: Low Memory', 'D:\Data\TempFiles\MemoryRpt.txt'
The stored procedure in Listing 1
contains simple error handling to prevent Blat
from wasting CPU cycles. For example, if an @To
variable is not populated, the process aborts. Although this particular code doesn't validate the email address, you could easily add code to do so. The @cmd
variable contains the constructs of the command-line utility, as shown in Table 1.
|Table 1. The Constructs of the Command-Line Utility|
||The body of the message is at the end of the parameter.
||To email address
||A newer syntax that works well for authenticated connections
||From email address
||Display name for your email address
||Organization name; a great place to identify the name of your company
||Email header information
||Prevents your header information from displaying Blat's homepage
||Prevents a header entirely
||Email server IP or name
||Typical SMTP port is 25.
||Your email message; for small reports, you could use this part instead of an attachment.
If you have no attachment, just leave that field empty and the procedure will ignore the construct in the command line.
|Author's Note: Running this process involves using xp_cmdshell. That means your average users can't execute it. Consider queuing messages in a table and then having an alert job run against the table. Another method is to set up a SQL Server proxy agent user account that allows users to execute xp_cmdshell. Be careful with this method because it could compromise your server's security.|