When you use Database Mail to send emails in SQL Server, you can use the sysmail_delete_log_sp stored procedure to delete items from the event log.
You can choose to delete all events, events based on their logged date (i.e. before a certain date) or events based on the event’s type.
Continue readingSQL Server provides the ability to send emails via its Database Mail solution.
The actual act of sending mail is done with the sp_send_dbmail stored procedure. But before you start sending emails from SQL Server, you need to enable and configure Database Mail.
You can do this with the SSMS GUI, or with T-SQL.
This article demonstrates how to do it with T-SQL. It assumes that Database Mail has never been enabled on your system, and therefore it goes through the steps involved in enabling it.
If you prefer to use the SSMS GUI, see How to Setup Database Mail in SQL Server (SSMS).
Continue readingWhen you use Database Mail to send emails from SQL Server, email messages and their attachments are stored in the msdb database. You should periodically delete these messages to prevent the database from growing to large.
To delete these messages with T-SQL, use the sysmail_delete_mailitems_sp stored procedure.
You can delete mail messages based on their send request date (i.e. before a certain date) or based on their status. You can also delete all mail messages by using the current date as the request date.
Continue readingIf you’re using Database Mail in SQL Server, you can change the configuration settings by executing the sysmail_configure_sp stored procedure in the msdb database.
If you’re using Database Mail in SQL Server, you’ll probably want to check your configuration settings at some stage.
You can do this by executing the sysmail_help_configure_sp stored procedure in the msdb database.
If you’re trying to check an advanced configuration option in SQL Server, but you get an error, you might find the following helpful.
Continue readingIn SQL Server, you can use a logon trigger to audit and control server sessions, such as track login activity, restrict logins to SQL Server, or limit the number of sessions for a specific login.
This article provides an example of using a logon trigger to limit the number of simultaneous sessions for a specific login.
Continue readingIn SQL Server, you can use the sys.server_trigger_events catalog view to return a list of server trigger events.
More specifically, this view contains one row for each event for which a server-level (synchronous) trigger fires.
Continue readingIn SQL Server, you can use the sys.server_triggers catalog view to return a list of server triggers.
More specifically, this view contains the set of all server-level DDL triggers with object_type of TR or TA.
For CLR triggers, the assembly must be loaded into the master database.
You can use the sys.triggers catalog view to return a list of triggers in a database in SQL Server.
This view contains a row for each object that is a trigger, with a type of TR or TA.
Continue reading