It is difficult to organise routing based on applications that make connections, but fairly easy by IP address if you can work out a routing scheme that has a default for non-work items, and then specific routes for work related destinations.
So in the scenario you describe, you want your wireless to do most things, and happens to be the types of activities that you could write specific routes for, so this should be the default route. Accept the IP address and default route from the wifi connection.
The cable is to be used for specific things, such as
- sql connection
- software development
Normally these types of activities are to specific and known servers. All you need is their IP addresses, and you can route requests to these servers via the cable connection.
If you have to get an IP by dhcp for the cable connection, you'll need to delete the default route they provide you:
route delete 0.0.0.0 mask 0.0.0.0 <cable next hop>
Then add specific routes for the servers you want to connect to via cable:
route add <rdp server ip> mask 255.255.255.255 <cable next hop>
route add <sql server ip> mask 255.255.255.255 <cable next hop>
route add <dev server ip> mask 255.255.255.255 <cable next hop>