In SQL Server, you can use the sysmail_help_profile_sp stored procedure on the msdb database to retrieve a list of all Database Mail profiles.
You can also return profile info based on the profile name or ID.
In SQL Server, you can use the sysmail_help_profile_sp stored procedure on the msdb database to retrieve a list of all Database Mail profiles.
You can also return profile info based on the profile name or ID.
In SQL Server, you can use the sysmail_help_principalprofile_sp stored procedure on the msdb database to retrieve a list of all associations between Database Mail accounts and database principals.
You can also return account info based on the principal name/ID or the profile name/ID.
In SQL Server, you can use the sysmail_help_account_sp stored procedure on the msdb database to retrieve a list of all Database Mail accounts.
You can also return account info based on its account name or ID.
You might be familiar with the ALL option in SQL Server. Perhaps you’ve used it along with the UNION operator to include any duplicates that might be returned in the result set.
But did you know that ALL can also be used in two other contexts?
ALL can be used in the following three contexts:
SELECT clause.UNION clause.Examples of each of these contexts follows.
SQL Server has an ANSI_NULLS setting that determines how NULL values are evaluated when compared to another value with the Equals (=) and Not Equal To (<>) comparison operators.
While it’s true that you can change the ANSI_NULLS setting at the session level (using SET ANSI_NULLS), each database also has its own ANSI_NULLS setting.
You can check your database to see whether its ANSI_NULLS setting is ON or OFF.
To do this with T-SQL, you can either use the sys.databases catalog view or the DATABASEPROPERTYEX() function.
In SQL Server, you can use the sysmail_help_status_sp stored procedure on the msdb database to check the status of the Database Mail queues.
If you use Database Mail in SQL Server, you can use the sysmail_sentitems view to return a list of all emails that Database Mail has sent.
If you use Database Mail in SQL Server, you can use the sysmail_allitems view to check the status of all emails that Database Mail has processed.
If you’re trying to send email using Database Mail in SQL Server, but it fails to send, you can check the sysmail_event_log view to see why it failed.
The sysmail_event_log view returns one row for each Windows or SQL Server message returned by the Database Mail system. By “message”, I don’t mean the actual mail message. I mean a message such as the error message that explains why the mail failed.
You can also use the sysmail_configure_sp stored procedure to determine what types of messages are logged.
If you’re trying to send mail with SQL Server but it’s not being delivered, try checking the sysmail_faileditems view.