Preventing Accidental Schema Changes To The master Database

If you have ever run some SQL within SQL Server Management Studio only to realise that you've run it against the master database by mistake, you'll know that it can sometimes be hard to undo the damage. A simple way to stop these accidental changes is to create a database trigger that will prevent any schema changes to the master database.