Skip to main content

Configure SQL Server Agent Mail to Use SQL Mail.


Hi all,

This topic describes how to use SQL Server Management Studio to set up SQL Server Agent Mail to use SQL Mail. Before you can use SQL Mail, you must enable SQL Mail and set up a mail profile. SQL Mail can be enabled by opening the Properties dialog box from the SQL Mail node, by using the Surface Area Configuration facet of Policy-Based Management, or by the using the sp_configure stored procedure.



1) In Object Explorer, expand a server.

2) Right-click SQL Server Agent, and then click Properties.

3) On the Alert System page, click Enable mail profile. If this option is not available, enable SQL Mail and set up a mail profile.

4) In the Mail system list, choose SQL Mail.

5) In the Mail profile list, select the Extended MAPI mail profile you created for SQL Mail. For more information about configuring a mail profile, see How to: Configure Mail Profiles for Use by SQL Mail (Windows).

6) Restart the SQL Server Agent service for your changes to take effect. For more information, see How to: Restart the SQL Server Agent Service (SQL Server Management Studio).

7) To test SQL Mail, send a test message using xp_sendmail.

Thanks & Regards,
Saurav Dhyani

Comments

Popular posts from this blog

Welcome - Microsoft Dynamics 365!

Hi All, In this article we will discuss the new introduced member of Dynamics Family. Yes you heard it correctly, one more new member with Name "Microsoft Dynamics 365" . #ProjectMadeira   #Dynamics365

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.