Scenario:
Multiple users access a SQL server database that is both local to there machine and centralized at location X. Location X is the master DB. Some users do not have consistent connectivity to the location X DB so they work off of there local DB. Ideally at the end of the day the user links to the net and sends a .bak of there DB to the master DB at location X and then restores that local DB to locations X’s DB. I guess the other part would be to create a .bak of Location X’s DB and then restore it to the users local DB.
Does this even make sense?
Can this be an automated process or does it need to be done manually?
Multiple users access a SQL server database that is both local to there machine and centralized at location X. Location X is the master DB. Some users do not have consistent connectivity to the location X DB so they work off of there local DB. Ideally at the end of the day the user links to the net and sends a .bak of there DB to the master DB at location X and then restores that local DB to locations X’s DB. I guess the other part would be to create a .bak of Location X’s DB and then restore it to the users local DB.
Does this even make sense?
Can this be an automated process or does it need to be done manually?
