Undefined outcome on schemarouter query conflict

When a query targets databases that are on two different servers, the schemarouter will route it to the first server that is parsed. This causes somewhat unexpected behavior when a better alternative is to route it to the server which contains the current active database. The current database is a lot easier to control compared to the order the database appear in the query itself.