Nang H. Vu - Learn and Fun Home Page

Home

History
Contact Me
A - B
C - D
E - F
K - L
M - N
O - P
S - T
U - V
Z - W
Family and Relatives
Relatives - Page 1
Lasan Taberd - School
Lasan Taberd Student List
Lasan Taberd - Page 1
Lasan Taberd - Page 2
Lasan Taberd - Page 3
Lasan Taberd - Page 4
Lasan Taberd - Page 5
Lasan Taberd - Page 6
Lasan Taberd - Page 7
Taberd - Class 10 Year 1969
Taberd - Class 11 Year 1970
Taberd - Class 12 Year 1971
Friends - Page 1
Friends - Page 2
Friends - Page 3
Friends - Page 4
Friends - Page 5
Expatiatory
S - T

SQLMai and SQLAgentMail

If were managing a single server or two, alerts and notifications may not be a big deal to us (though Id still be debating that alerts and notifications are invaluable here, too). But if were managing multiple boxes, were very reliant on automatically generated messages from the servers to let us know whats going on (or at least, if we do, our job again becomes easier).

Heres where SQLMail and SQLAgentMail come in.

Its SQLAgentMail that sends out alerts and notification via e-mail. However, if there is a need to run SQLMail as well (this can be very handy if we want to process queries by e-mail or send an e-mail in a batch job or stored procedure), then its usually best to use the same user account for both MSSQLServer (which uses SQLMail) and SQLServerAgent (SQLAgentMail). This means only one mailbox has to be created on the mail server and only one profile has to be set up on the SQL Server itself. By the way, this is the recommended practice by Microsoft, according to Books Online.