Unanswered: Dump Database Coming through in Replication
Database Dump commands that are wrapped in an explicit transaction are being replicated and wind up failing at the replicate and bringing down the connection. Whats the best way to filter these out ? Is there a settable option ?
the trick to work around this issue is to have a login trigger on the login that uses dump in an explicit transaction. The login trigger should simply set replication off. This way the dump will never be sent across.