I am building a desktop application that I want to get different people's opinions on how you would store the data. Below are some of the requirements.
1. There will be 3-4 computers networked together WITHOUT internet access
2. Each computer will be gathering data and need to store in the central database
3. There needs to be a backup of the data on a different computer other than the central database incase the main system crashes
4. If the main system crashes, I will need to change all of the systems over to use the backup database and easily change it to start backing up to another system (incase another crash)
1 answers
my advice for you is to start reading about db backups. if you are using Microsoft SQL server 2005 you have these two options: Logshipping "which gets all the Transactions done to the backup db pc", or mirroring which directly reflect any change on the primary database to the backup database on the other pc. But since the application is for 3-4 computers "which is supposed to be a small application", then normal backup on an external hard disk would be enough, like a job that makes a backup at night or at OFF-PEAK time and store the backup on external harddisk.
answered one month ago by:
663
71
How about adding a command to copy the database file onto a specified path on user's computer in the Fome_close event????
71
I mean.... Form_close event
663
unfortunately this can't be a good thing to do in database backup at all. usually the backup is timed or done as the two options written above since when you talk about db you must have in mind the size, for example the db i work on reached 400gb what hd will hold this backup on form close?