Whenever i read about those news, i never think i will face it one day by myself. My organization has 1 database server running SQL Server 2016 SP1 (GDR)face this issue.
This server was hand over to me from our developer. The server has no SQL Database Backup, No maintenance scripts, No Alerts for critical status or job fail, and not even have a Database Mail profile setup.
I prepare it all ready and stuck with the problem that the failed job alert was never received. Finally, i read from blog that ppl has find out the database mail is not working without .NET 3.5 for SQL Server 2016 and SQL Server 2016 SP1.
Initially, i am thinking install the .NET 3.5 for the server. However, it is not been approved by the application manager unless we conduct a impact analysis to the running application.
Microsoft has claimed the issue get fixed in CU2 of SQL Server 2016 SP1 on March 2017.
I also read carefully about the updates from below site:
Options in front of me are:
1 – Install SQL Server 2016 SP1 CU2
2 – Install SQL Server 2016 SP1 CU15 (the latest CU, release on May 2019, but end of support on July 2016)
3 – Install SQL Server 2016 SP2
Either CUs or SPs should of course been tested in developing and staging system and then apply to production system.
However, the challenge to me is the developing and staging database was running on SQL Server 2012. There is no other database server in the organization running SQL Server 2016.
However, the database mail is really imported to DBAs, as it is our ‘eyes’ and ‘ears’.
I may use option 2. Reason is the SP1 CUs are more mature and our SQL Server is far behind the patches level. Although SP1 is end of support, but CU15 is the last CU before it end of support.
I will definitely recommend our application team to upgrade their SQL server to be the same version as the production system. At that time, I could test SP2 fully before apply it to production system directly.