Alert on long-running queries with a five-minute SQL Agent job, a deduplicated log, and one Database Mail notice per new request.
SQL Agent Operators and Notifications: Who Gets the Alert
Configure SQL Agent operators, connect jobs and alerts to email notifications, test delivery, and verify notification evidence.
Database Mail Health Check: Unsent Items and the Event Log
The alert job succeeded, yet nobody got the email. Here are three read-only checks that show whether Database Mail is really working.
SQL SERVER – Database Mail Error: The SMTP Server Requires a Secure Connection or the Client Was Not Authenticated. The Server Response Was: 5.5.1 – Using Gmail
In my earlier blog, we saw one possible cause database mail error due to SSL settings. Today we will learn about another Database Mail Error.
SQL SERVER – Database Mail Error: The SMTP Server Requires a Secure Connection or the Client was not Authenticated. The Server Response Was: 5.5.1
Database Mail with Gmail failed: the SMTP server requires a secure connection or the client was not authenticated, 5.5.1. Here is how to fix it.
SQL SERVER – sp_readrequest – Long Running Process
sp_readrequest kept showing up as a long running procedure. It is Database Mail waiting on its queue with a 600 second timeout, usually nothing to worry about.
SQL SERVER – Script level upgrade for database ‘master’ failed – There is already an object named ‘DatabaseMailUserRole’ in the database
After patching, script level Upgrade for master failed: there is already an object named ‘DatabaseMailUserRole’. Here is what caused it and how to fix it.