I also had this same thought for a brief moment, but triggers are not fired for truncate table statements, and there may occasionally be a legitimate need to delete or update more than (x) rows. I second the motion to remove users from SYSADMIN, DBO, or DATAWRITER roles and instead grant them execute permission on a parameterized stored procedures which contains the proper logic. If end users can ad-hoc write to the database, there are 100 different ways they can screw up the tables. For example, they can open an SSMS connection to production by mistake thinking it's development, or they can get the source and destination servers switched around when attempting to import data from tables in production to QA.