To study some specific customer issues, I have a copy of their production database running on a separate machine. The database has CLR assemblies and some complex legacy code to call external services through triggers and stored procedures.
I would like to prevent accidental calls of the external production services without having to inspect all the triggers one by one or disabling all the triggers.
What would be the easiest way to block all outgoing network requests of an SQL server instance and how do I test that the block is really active, so I can safely work with the database without any danger of sending data to external services?