Create the trigger after modifying your mail profile settings, and any additional attachment types if you wish.
Simple technique to ensure you are informed if any content is written.
CREATE TRIGGER usr_suspect_page
@profile_name = 'yourmailprofilename',
@recipients = 'email@example.com',
@subject = 'Suspect page row written - check details',
'select * from msdb.[dbo].[suspect_pages]',
@attach_query_result_as_file = 0, --set to 1 for true, this script will keep results in email body
@query_attachment_filename = 'msdb_suspect_rows.csv' -- will only attach when prior parameter set TRUE
Corrupt SQL Server databases are the worst nightmare of any SQL Server professional. In any environment, from small business to enterprise, the compromise of integrity and availability of the data can constitute a business emergency. This is especially the case in those organizations reliant on an OLTP data model, for a high-volume website. SQL Server database corruption and disruption of the transaction processing system can cause business repercussions such as large financial losses, a drop in reputation or customer retention, or contractual SLA problems with the service provider, if not managed in-house.