SQL Mail to be deprecated in Microsoft SQL Server 2008 R2

If your organization is considering upgrading to Microsoft SQL Server 2008 R2 and relies on SQL Mail to generate Business Alerts notifications for Microsoft Dynamics GP, then this is for you.

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:

Deprecated Database Features in SQL Server 2008 R2


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!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Anonymous said…
Hi,
Does it mean that the Emailing Statement option under Customer Master can now email statement using DB Mail and the requirement for MAPI compliant email client is taken out?

May
GP User
June 21, 2010 at 12:03 PM
Mariano Gomez said…
Not sure I understand your question. The statements emailing capability in GP does not rely on SQL DB Mail, but rather a MAPI profile as it uses Outlook to send emails.

MG.-
June 21, 2010 at 4:58 PM
Joe said…
I found this blog while researching SQL Mail vs Database Mail. I'm running Dynamics 2010 GP. This version utilizes "xp_findnextmsg" type in it's stored procedures. I wanted to use Database Mail. I don't think Dynamics supports it. Dynamics would need to be updated to use "sp_processmail", "sysmail_start_sp", and more which are stored procedures from SQL Server. Does this sound correct? I only wanted to enable the "Paging/Emailing" feature in the Field Service Module. I think I'm stuck using SQL Mail which means I need to setup outlook on the SQL Server. I don't like the fact the if SQL Mail crashes, so does MSSQLSERVER...
January 22, 2013 at 12:55 PM
Mariano Gomez said…
Joe,

I'm not sure I am following. SQL Mail is still supported under SQL Server 2008 R2 (it is no longer supported in SQL Server 2012, however), hence xp_findnextmsg and sp_processmail still work. As you mentioned though, you would need Outlook to be able to send and retrieve messages as SQL Mail uses MAPI.

In fact, if using Database Mail, all stored procs must be updated to use sp_send_dbmail - Database Mail uses SMTP.
January 22, 2013 at 10:18 PM
Post a Comment

Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

Image
In this video, learn to enable Power Apps Application Monitoring with Azure Application Insights.  The following topics are covered in this video:  ( 0:00 ) - Intro  ( 0:36 ) - What is Azure Application Insights  ( 1:32 ) - The timesheet app  ( 2:12 ) - Creating an Application Insight for the timesheet application  ( 3:55 ) - Identify and copy the application instrumentation key  ( 4:09 ) - Enabling the timesheet application with the instrumentation key  ( 5:32 ) - Working with Application Insights  ( 8:06 ) - Outro For additional information on Azure Application Insights, please follow these resources: Microsoft Docs - What is Azure Application Insights? here Adam Marczak - Azure for Everyone: Azure Application Insights Tutorial, here To check out my YouTube channel visit: https://youtube.com/user/mgomezb1 LIKE AND SUBSCRIBE!!! Until next post! MG.- Mariano Gomez, MVP
Read more

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics
Read more

eConnect Integration Service for Microsoft Dynamics GP 2010

Image
One of the biggest improvements in eConnect 2010 is the addition of the new eConnect Integration Service . The eConnect installer now creates a new Windows Service application named eConnect for Microsoft Dynamics GP 2010 integration Service . The eConnect Integration Service is a Windows Communication Foundation (WCF) service that replaces the (very unstable) eConnect COM+ object available in previous versions of eConnect. The eConnect Integration Service supports the operations of the eConnect .NET assemblies, the BizTalk adapter, and MSMQ interfaces. In addition, you can use the service directly from an application that adds a service reference to the eConnect Integration Service. If you add a service reference, you do not need to add the Microsoft.Dynamics.GP.eConnect assembly and namespace to your development project. To add the eConnect Integration Service to an application, you must first add a service reference to the Visual Studio project for that application. To add a servi
Read more