Yeah! A trigger that deletes any sensitive information pertaining to the good folks in the SQL Server Central community would suit just fine. Nobody seems to notice triggers in production systems. 🙂

This is an issue that really bothers me. A friend of mine was mistakenly put onto a government database in the UK because he has the same name as a convicted criminal. Of course, he wasn't aware that it had happened. For reasons he couldn't work out, suddenly simple things like getting a loan, getting a job, participating in societies and so on became hugely difficult. He only found out about the error when he persisted in wanting to know why he was turned down for a job.