SQL Mail and SQLAgentMail can use the same or different mail profile. If necessary, each mail profile can be configured within its own domain account.
When configured, mail profiles are specific to the Microsoft® Windows NT® 4.0 or Windows® 2000 user domain account that is activated when a user logs on to Windows NT 4.0 or Windows 2000 successfully. SQL Mail must have a mail profile created in the same user domain account or context that is used to start an instance of Microsoft SQL Server™. When a mail stored procedure is executed, SQL Mail looks for the defined mail profile in the domain account that triggered it.
If you plan to use mail stored procedures you must:
To configure a mail profile
To set up SQL Mail
If you plan to send notifications to operators by e-mail or pager, you must:
A mail profile is required by SQLAgentMail to start a mail session and send notification by e-mail or pager. A SQL Server Agent mail session is started every time that the SQLServerAgent service is started. You can create the profile with a mail client, such as Microsoft Outlook®, that is installed locally on the SQL Server computer.
To configure a mail profile
To set up SQLAgentMail
SQL Mail and SQLAgentMail sessions may be configured to use the same Windows NT 4.0 or Windows 2000 domain user account. When using the same domain account, SQL Mail and SQLAgentMail can share the same mail profile using a common mailbox.
SQL Server uses two separate mail sessions:
SQL Server uses this mail session when database applications execute the xp_sendmail extended stored procedure to send a message or query result set to a recipient.
You can configure separate mailboxes for SQL Mail and SQLAgentMail by creating separate mail profiles. There are two ways to accomplish this:
For more information about setting up and configuring mail clients and mail profiles, see the Windows NT 4.0 and Windows 2000 documentation.