Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Let's say the database is non-sql, something completely archaic like paradox or whatever. I have no power over it as I'm not the developer. However, I would really like to have the database live on a cloud and get synchronized immediately upon changes.

The software requires "local machine" or at the very least "local network" access to the database, which means "C:\db\db.db" or "\server\db\db.db".

But I was thinking of using SkyDrive like "C:\User\Skydrive\db\db.db", but struck me that it might not work the way I want it to.

So I wanna hear opinions and alternatives to what I want to do (maintain the database on the cloud so I don't have to back it up all the time)

share|improve this question
Using SkyDrive like this, with multiple users (or one user on different computers) will not work. Changes will not be properly merged when they conflict. – Nate Mar 12 '13 at 14:32
Would that actually be used by different users or different computers at the same time? If the software/database you're writing about is not done for concurrent access, putting it anywhere on a cloud or in a networking situation will not solve anything but only create problems. – Tonin Mar 12 '13 at 14:50
Cloud is no replacement for a backup. If you just have the DB with a "cloud provider" and he frakks up, what do you do then? – Sven Mar 12 '13 at 14:56

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.