https://www.sqlserver70.com/tags/sysmail_account/Recent content in Sysmail_account on SQL Server ScriptsHugo -- gohugo.ioenSQLServer70.comWed, 01 Jul 2026 00:00:00 +0000https://www.sqlserver70.com/post/sql-server-database-mail-configuration-and-test-script/Wed, 01 Jul 2026 00:00:00 +0000https://www.sqlserver70.com/post/sql-server-database-mail-configuration-and-test-script/ <p>Database Mail ships disabled; enabling it and wiring up an SMTP account, a profile, and a public principal grant are the steps that stand between a fresh SQL Server instance and <code>sp_send_dbmail</code> working reliably. The configuration script below executes all four setup calls inside <code>msdb</code>, fires a test message, and queries <code>msdb.dbo.sysmail_event_log</code> to confirm the message reached the SMTP relay — all in one repeatable script.</p> <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:inline-block;width:728px;height:90px" data-ad-client="ca-pub-1012089347386563" data-ad-slot="8593449130"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> <h2 id="purpose-and-overview">Purpose and Overview</h2> <p>Sending email from SQL Server — for Agent job failures, custom monitoring alerts, or ad hoc DBA notifications — runs through a single pathway: an SMTP account registered in <code>msdb</code>, wrapped in a named profile, and exposed to the Database Mail service via a principal-profile grant. When any of those three links is missing or misconfigured, <code>sp_send_dbmail</code> accepts the call and silently queues the message, but the mail never leaves the server. The only diagnostic path is <code>msdb.dbo.sysmail_event_log</code>.</p>