Is there a reason you can't use multiple OLE db destinations? That would likely be the best way ... get the data from your source, do a conditional split on city and map each condition to a seperate ole eb destination with a connection to the appropriate server.

If you really don't want that, you could probably put your data flow in a for loop container, and put an expression in your ole db destination that changes the connection used (or connection string if you only want to define one connection too) based on your iteration of the loop.

Upside is it would be easy to add more city/server destinations in the future. Downside is you query the source multiple times instead of getting all the data and splitting it.