Ars Technica

Getting the SQL statement that caused a trigger to fire [T-SQL]

I have a 3rd party app that I suspect is behaving badly (actually, I'm about 99.9% sure it is). When I save changes to the database, it executes what should be (as near as I can tell) about 20 SQL ...
CSOonline

JSON-based SQL injection attacks trigger need to update web application firewalls

Security researchers have developed a generic technique for SQL injection that bypasses multiple web application firewalls (WAFs). At the core of the issue was WAF vendors failing to add support for ...
ITWire

iTWire - Using database triggers for alerting and auditing

Within the trigger code we extract fields from table inserted, construct a message and then send this via e-mail using SQL Server's msdb.dbo.sp_send_dbmail stored procedure. Note that in the below ...
Ars Technica

MS-SQL Trigger Issue

Like all good problems, this one is sporadic and seemingly senseless, but I figured maybe somebody here would have some suggestions on possible causes of the situation to be laid out. For our app, we ...
ITWire

iTWire - Using database triggers for alerting and auditing

We create a trigger using the T-SQL 'create trigger' command, specifying both the table to monitor (PurchaseOrders) and the actions that cause it to fire (insert, update). Within the program code we ...