Synchronizing SQL Data with or without a VPN?

You stuck your updates into an XML payload, use SEND to upload the changes, the message activates a procedure on your back end, it sherds the XML payload back into table updates. You can put an Express instance on the DMZ to act as gateway and rely on the built-in Message Forwarding Since Service Broker can use certificates for authentication no VPN is required. Also you solve the problems of availability, the updates are queued up and delivered whenever there is connectivity.

You stuck your updates into an XML payload, use SEND to upload the changes, the message activates a procedure on your back end, it sherds the XML payload back into table updates. You can put an Express instance on the DMZ to act as gateway and rely on the built-in Message Forwarding. Since Service Broker can use certificates for authentication, no VPN is required.

Also you solve the problems of availability, the updates are queued up and delivered whenever there is connectivity.

stunnel.org/ Provides a wrapper that encapsulates a network connection in SSL encryption.

You could use email with your data as an attachment. You can process emails at your server with an automated agent. Distributing updates the other way might be more difficult - your user would have to save your attachement and then run a local importer.

Plus the timing issues of when they decide to do this could be tricky to work out. But it might work better depending on your user base.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.