Answered by:
remote and local database syncronization

Question
-
Dear Team,
I have a small question, basically i am working in NGO as MIS specialist and i have a question i.e. we have our central database (SQL server 2008) over cloud and users connect from our application(Windows base software) to that , we have different offices in different countries , sometime it happens user dont have internet or they have some problem with the internet so we like to have local Sql server in their premises and it should sync with realtime central database always so whenever internet get fail or some problem occur and internet stop working so they can work with the local sql server database and once internet start working we want to update our records what they entered during offline to central database. please suggest how can we achieve this.
Regards
EliSunday, January 11, 2015 3:10 PM
Answers
-
Hi aliImranrizvi,
According to Uri’s post, you could use replication to achieve your goal. Merge replication fits your scenario best among replication types. Merge replication allows various sites to work autonomously and later merge updates into a single uniform result. And it is usually used when there is no constant network connectivity among publishers and subscribers. It enables sites to merge the changes to the data when they are next online. For how to set up merge replication, please refer to the article: http://blogs.technet.com/b/meamcs/archive/2011/01/06/merge-replication-step-by-step.aspx.
In addition, because updates are made at more than one node, the same data may have been updated by the Publisher and by more than one Subscriber. Therefore, conflicts can occur when updates are merged and merge replication provides conflict resolver to handle conflicts. For more information about merge replication conflict detection and resolution, please refer to the article: http://msdn.microsoft.com/en-us/library/ms151257(v=sql.110).aspx
Regards,
Michelle Li
- Edited by Michelle Li Monday, January 12, 2015 6:57 AM
- Proposed as answer by Michelle Li Friday, January 16, 2015 1:07 PM
- Marked as answer by Lydia ZhangMicrosoft contingent staff Monday, January 19, 2015 3:32 AM
Monday, January 12, 2015 6:57 AM
All replies
-
Take a look into Replication if it is possible in your scenario...
Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting: Large scale of database and data cleansing
Remote DBA Services: Improves MS SQL Database Performance
SQL Server Integration Services: Business Intelligence
Monday, January 12, 2015 6:36 AM -
Hi aliImranrizvi,
According to Uri’s post, you could use replication to achieve your goal. Merge replication fits your scenario best among replication types. Merge replication allows various sites to work autonomously and later merge updates into a single uniform result. And it is usually used when there is no constant network connectivity among publishers and subscribers. It enables sites to merge the changes to the data when they are next online. For how to set up merge replication, please refer to the article: http://blogs.technet.com/b/meamcs/archive/2011/01/06/merge-replication-step-by-step.aspx.
In addition, because updates are made at more than one node, the same data may have been updated by the Publisher and by more than one Subscriber. Therefore, conflicts can occur when updates are merged and merge replication provides conflict resolver to handle conflicts. For more information about merge replication conflict detection and resolution, please refer to the article: http://msdn.microsoft.com/en-us/library/ms151257(v=sql.110).aspx
Regards,
Michelle Li
- Edited by Michelle Li Monday, January 12, 2015 6:57 AM
- Proposed as answer by Michelle Li Friday, January 16, 2015 1:07 PM
- Marked as answer by Lydia ZhangMicrosoft contingent staff Monday, January 19, 2015 3:32 AM
Monday, January 12, 2015 6:57 AM