• You can set up a virtual network that allows you to treat the VMs as if they were part of your on-premises servers. Then, you have lots of choices. You can set up any of the standard methods for moving data around, including replication, availability groups, log shipping, whatever you think will work best. But start by getting the virtual network setup. Just remember, any method you use needs to take into account two issues, availability and latency. There is a likelihood of connection issues, so you have to have a good retry mechanism. And, depending on where your home base is, you're going to see latency. But neither of those should prevent you using just about any mechanism for moving the data around.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning