With the introduction of Microsoft SQL Server 2008 R2, a number of database features will be deprecated, this is, the feature will not be available in a future release of SQL Server -- SQL Mail being one of them. You can find the complete list of features that will be deprecated here:
A couple things about SQL Mail:
1. SQL Mail runs in-process to SQL Server service. The issue here was, if SQL Mail crashed so did your SQL Server. Certainly, not an optimal situation in a production environment.
2. Using SQL Mail requires installing an extended MAPI client component on your server. Most of you would have typically resorted to install Microsoft Outlook to overcome this situation, as without a MAPI client SQL Mail would not run.
So here comes Database Mail:
1. Unlike SQL Mail, Database Mail runs in a separate process thread. If Database Mail goes down, it will not take down SQL Server with it.
2. Database Mail does not require an extended MAPI client component for it to run.
3. Database Mail can be configued with multiple SMTP accounts and with multiple profiles. This increases the robustness of the system. In a realtime environment, if one mail server goes down, Database Mail will still be able to send emails through the other configured SMTP accounts.
4. In Database Mail, all mail events are logged keeping history of emails.
5. You can configure Database Mail to limit file sizes, disallowing large attachments and filtering of file extensions such as .exe or .bat
To configure Database Mail please check the following Microsoft video:
Video source: Technet (http://technet.microsoft.com/en-us/sqlserver/dd939167.aspx)
Be sure to include Database Mail setup as part of your SQL Server 2008 R2 implementation and to test all your Microsoft Dynamics GP Business Alerts in the process.
Until next post!
Mariano Gomez, MVP
Maximum Global Business, LLC