Originally Posted by rsk
as someone with 2 BES domains (and over 7000 devices) I would highly reccommend against it. you will create more problems than you solve by doing it.
1. add a new BES server in WI an connect it to SQL in CA.
2. move users from old server to new server.
let BES worry about latency to SQL, it should not cause message delivery delays as Exchange is local to BES, and it will save you many administrative problems. (users activated on 2 bes domains, devices on both domains, moving users from one domain to another requires re-activation) and then there is reporting from 2 domains instead of 1, maintaining 2 sets of IT policies, etc etc etc..
I agree but he is saying that connection between two sites are not reliable and that there might be disconnection between them. Other then that I have couple of dozen BES servers all over tyhe country and they are all connected to a same SQL. Some of them with high latency but reliable link between. No problem so far.