Lior: Have you considered locating the server somewhere in the middle in west Europe?
I was going to make this suggestion too but Lior got there first
More to the point I would be very wary of trying to do this, especially with someone who is "just" an SQL Server expert and not familiar with how Priority works
Distributed databases are a challenge at the best of times
Priority is not designed for this sort of thing
If you have two systems which you are trying to sync then you have to deal with new identifiers being added in both places and then resolving the clashes. You don't want to risk the integrity of a business system in this way
Also Priority has a lot more parts than just the database. It's critical that everything works together. There is a "file system" part of the system where compiled versions of forms and procedures and so on are kept and that is expected to be a single repository for everyone . If a form is marked as changed then it will recompile on one side and the new file will be saved and then the form marked as compiled. That detail would be synced to the other database and you'd also have to make sure that the file is copied over too. This would presumably need to happen in both directions
If the only need is to have a local copy (read only) of the database at the second location then it would be adequate to replicate in one direction and then a DBA could help (for SQL Server there is a program in Priority to put the necessary primary keys in the database to allow setting up that replication without the keys being a surprise to Priority). But from your question it seems that you have active users at the remote site
Basically I want to say that I don't think this is a feasible idea
If your remote users need access to only a small set of data and to make specific updates then you might be better off with a custom system with its own backend database and a sync strategy between that and Priority. Alternatively maybe the generic mobile application systems for Priority which can also work offline would suffice as they may handle the latency issues better than those applications which need to contact the Priority server directly
I hope that this has been helpful
